-
Notifications
You must be signed in to change notification settings - Fork 0
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
Update can-map-define to the latest version 🚀 #11
base: master
Are you sure you want to change the base?
Conversation
Version 4.1.0 just got published. |
Version 4.1.1 just got published. |
Version 4.2.0 just got published.Update to this version instead 🚀 Release Notesv4.2.0CommitsThe new version differs by 10 commits.
See the full diff |
Version 4.3.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 6 commits.
See the full diff |
Version 4.3.1 just got published. |
Version 4.3.2 just got published. |
Version 4.3.3 just got published. |
Version 4.3.4 just got published.Update to this version instead 🚀 Release Notesv4.3.4getOwnEnumerableKeys accounts for default behavior valuesThis patch release fixes an issue with var VM = CanMap.extend({ define: { "*": { serialize: false }, notEnumerable: { value: "no" }, enumerableProp: { serialize: true, value: "yes" }, notEnumerable2: { serialize: false, value: "maybe" } } }); That meant, calling |
Update to this version instead 🚀 Release Notes for Update to use Symbol instead of `__inSetup` propertyInstalled latest Ref - canjs/canjs#4705 CommitsThe new version differs by 12 commits.
See the full diff |
|
|
|
|
☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.
Version 4.0.0 of can-map-define was just published.
The version 4.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of can-map-define.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Commits
The new version differs by 3 commits.
e463005
4.0.0
5967503
Merge pull request #64 from canjs/4
6294786
Upgrade dependencies to 4.x
See 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 🌴