Prepare Commonlib 0.1.12 - #110
Merged
Merged
Conversation
vrtmrz
marked this pull request as ready for review
August 12, 2026 16:40
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 updates Commonlib to 0.1.12 so Fast Fetch tombstones and inconsistent Metadata identities can be handled safely in an exact staged package.
Changes
package.jsonandpackage-lock.jsonfrom 0.1.11 to 0.1.12.Impact
Fast Fetch now writes deletion tombstones to the local database without attempting to decrypt their absent payload. Old deletions therefore no longer abort an initial fetch, while the deletion remains represented locally.
Offline scans now validate each decoded Metadata document against its actual database ID before target filtering or pair construction. An inconsistent entry remains unchanged and cannot trigger reflection, deletion, expired-history cleanup, or last-seen persistence. A separate, consistent entry for the same logical path continues normally.
Maintained hosts can inspect an inconsistent entry by its actual ID and explicitly repair one unambiguous entry at a time. This release does not infer how a mismatch arose, perform batch repair, rename Vault storage, choose between case variants, coordinate devices, or alter Fast Setup and CLI completion policy.
Verification
npm ciwith npm 11.18.0 succeeded.NODE_OPTIONS=--max-old-space-size=3072 npm run verify:package— 71 test files and 1,283 tests passed, together with seven boundary tests, 20 release-selection tests, type checks, package-boundary checks, 117 generated compatibility exports, and clean-consumer checks.npm run check:package— succeeded.npm publish --dry-run .package --tag next --access public— succeeded.sha512-7EQy1lsxQPGL5aBxx0aliBszZqF3XKzf+sHcEcS94oZF2MoFugoyxwqoxB/SuZ9gRbGAZDQYiD5R8Y+i6FRivA==The dependency graph is unchanged. Production audit reports 18 existing moderate advisories. The full development audit reports 19 moderate advisories and one high advisory; the high advisory is confined to the Vitest development dependency chain.