Repository navigation
release: prepare Commonlib 0.4.2 - #216
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.
This release preparation selects Commonlib 0.4.2 for opt-in recovery of unapplied logical deletions and corrected unbounded namespaced key enumeration.
The implementation was merged in #215. This PR changes only the source manifest version, matching lockfile version fields, and the dated release notes in
updates.md; dependencies and runtime source are unchanged.Release notes
Added
Fixed
Verification and publication
latestandnextboth pointed to 0.4.1.npm run test:release,npm run test:package, andnpm publish --dry-run .package --tag next --access publicpassed after the version change. The source manifest remains private.No package is published by this PR. After merge, stage the exact reviewed main commit through the trusted workflow to
next, verify the published registry artefact and applicable consumer checks, then promote that same version tolatest. LiveSync adoption remains in vrtmrz/obsidian-livesync#1341.