An in-range update of can-map is breaking the build 🚨 #77
Comments
|
After pinning to 4.0.2 your tests are passing again. Downgrade this dependency 📌. |
Version 4.1.1 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesv4.1.1Remove remaining uses of can-util #104 |
Version 4.1.2 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesnot binding on __keys during setup |
Version 4.2.0 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release NotesAdds Map.prototype._legacyAttrBehaviorAdds a To use it, you can either: // Sets the legacy behavior for all Maps can.Map.prototype._legacyAttrBehavior = true // Sets the legacy behavior for an individual map type Type = can.Map.extend({ _legacyAttrBehavior: true}}) // Sets the legacy behavior for a single map instance var map = new can.Map(); map._legacyAttrBehavior = true; CommitsThe new version differs by 9 commits.
See the full diff |
Version 4.3.0 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 12 commits.
See the full diff |
Version 4.3.1 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release NotesMakes deep assigns and updates work with _legacyAttrBehaviorWhen using map.attr({ prop: new DefineMap() }) This works with both assign and update forms of attr(). CommitsThe new version differs by 15 commits.
See the full diff |
Version 4.3.3 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release NotesHandles props with undefined valuesMakes sure that any props on the map are still added when their value is CommitsThe new version differs by 18 commits.
There are 18 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for Cleanup can-types.isMapLike(obj)Replace usage of CommitsThe new version differs by 28 commits.
There are 28 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for Use Symbol to replace __inSetup propertyReplace CommitsThe new version differs by 34 commits.
There are 34 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 38 commits.
There are 38 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 45 commits.
There are 45 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for Tests using canReflect.getName in assertions fail in IE11Test failed due to CommitsThe new version differs by 49 commits.
There are 49 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 56 commits.
There are 56 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for Prevent bubble parent with children functionsThis fixes bubbling the parent map with children functions as properties, for example: var map = new CanMap({ fn: function() {} }); CommitsThe new version differs by 61 commits.
There are 61 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for Prevent bubble parent with children arraysChildren array properties should not bubble parent: var map = new CanMap({ foo: ['item'] }); CommitsThe new version differs by 64 commits.
There are 64 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 68 commits.
There are 68 commits in total. See the full diff |
Version 4.1.0 of can-map was just published.
This version is covered by your current version range and after updating it in your project the build failed.
can-map is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
Status Details
Release Notes
v4.1.0Commits
The new version differs by 12 commits.
9c254c34.1.0b1a0524Merge pull request #100 from canjs/landscaper/4217-use-strict683a3e9Merge pull request #102 from canjs/can-util-removalc364b7eadd deps to package.jsonf29a064Merge pull request #98 from canjs/greenkeeper/testee-0.8.087de322remove can-util from package.json9e6adc9fix can-reflect use14fec0dget rid of can-util86d34a0Merge pull request #101 from canjs/fix-webpack-debug-stylef441961fix dev code for webpack compatibility3de0d54Adds use strict. Fixes canjs/canjs#42172303ec8chore(package): update testee to version 0.8.0See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
The text was updated successfully, but these errors were encountered: