Repository navigation
release: 0.16.1 - #37
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release 0.16.1.
Includes:
mapMergePatchleaves unchanged null-valued map keys out of the patch. An update of a map-valued field no longer re-sends the map's null-valued keys asnull, which deleted them on every peer (Jupyter: null-valued metadata keys are kept on import, then silently deleted by the first metadata edit cocalc-ai#1388, Jupyter metadata). Removed keys are still sent asnull; null-as-delete is unchanged. Wire-compatible: patches only get smaller.The only change is the version bump in package.json. After merge: tag
v0.16.1, and release.yml publishes to npm with provenance.