-
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-map is breaking the build 🚨 #33
Comments
After pinning to 3.0.7 your tests are passing again. Downgrade this dependency 📌. |
Version 3.3.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 3.3.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release NotesUndeprecated ArrayThis patch release is a purely internal change to use CommitsThe new version differs by 13 commits.
See the full diff |
Version 3.3.2 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release NotesUpdating can-stache-keyCommitsThe new version differs by 6 commits.
See the full diff |
Version 3.3.3 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 9 commits.
See the full diff |
Version 3.3.4 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 13 commits.
See the full diff |
Version 3.4.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release NotesPermissive handling for properties with dots.With can-map 3.2.0, handling of dotted properties (e.g. "foo.bar" as a property key in a can-map) was updated to throw fewer errors and allow more cases, but this was not documented as official behavior in the API. In this release, we've made those changes official in the API. For more information, see the "Properties with dots in their name" section in https://github.com/canjs/can-map/blob/v3.4.0/docs/prototype.attr.md CommitsThe new version differs by 16 commits.
There are 16 commits in total. See the full diff |
Version 3.4.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release NotesUpdated docs and added cycle detectionCommitsThe new version differs by 5 commits.
See the full diff |
Version 3.4.2 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv3.4.2Make the |
Version 3.2.0 of can-map just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As can-map 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 4 commits.
84f0afc
Update dist for release
94c393f
Update dist for release
63c8d44
fixing postversion script
5721a40
Works with can-reflect (#39)
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: