-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
An in-range update of can-fixture is breaking the build 🚨 #31
Comments
After pinning to 1.0.14 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Version 1.1.1 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release NotesRemove pre-release package referencesThe post-can-reflect releases from CanJS 3.9 are all stable, so packages shouldn't be depending on pre-releases now. CommitsThe new version differs by 13 commits.
See the full diff |
Version 1.1.2 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release NotesUpdated docs and added cycle detectionCommitsThe new version differs by 19 commits.
There are 19 commits in total. See the full diff |
Version 1.2.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 21 commits.
There are 21 commits in total. See the full diff |
Version 1.2.1 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesv1.2.1Fixes the npm package to include the |
Version 1.2.2 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv1.2.2Fixes an issue in which Array, FormData, and data types were converted to plain objects #133 (thanks @roemhildtg!) CommitsThe new version differs by 7 commits ahead by 7, behind by 1.
See the full diff |
Version 2.1.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv2.1.0CommitsThe new version differs by 26 commits ahead by 26, behind by 1.
There are 26 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 50 commits ahead by 50, behind by 1.
There are 50 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for support Promise and Async/AwaitThis release adds support for the CommitsThe new version differs by 59 commits ahead by 59, behind by 1.
There are 59 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 61 commits ahead by 61, behind by 1.
There are 61 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 62 commits ahead by 62, behind by 1.
There are 62 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 67 commits ahead by 67, behind by 1.
There are 67 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 71 commits ahead by 71, behind by 1.
There are 71 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 76 commits ahead by 76, behind by 1.
There are 76 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 79 commits ahead by 79, behind by 1.
There are 79 commits in total. See the full diff |
Version 1.1.0 of can-fixture just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As can-fixture is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
Status Details
Commits
The new version differs by 3 commits.
d09f1a7
Update dist for release
4d4987b
fixing postversion script
c3e6c53
Do Not Merge - can-reflect (#117)
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
The text was updated successfully, but these errors were encountered: