Repository navigation
Prepare 0.8.0 release and strengthen installed-package verification - #15
Merged
Merged
Conversation
Exact source local commit: ef2a8c1e059b8c40a72347a685f5fb47c0bef0a9 Verified tracked tree: 6f2f126 Original local history retained; remote SHA intentionally differs.
focaxisdev
marked this pull request as ready for review
October 18, 2026 03:27
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
1 participant
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.
Prepare 0.8.0 for additive opt-in engine APIs and carry forward the unpublished 0.7.1 reliability fixes. Correct the outdated deletion-recovery note and keep the homepage explicit that npm publication is pending.
Expand the existing package test with full path checks, credential-pattern checks, SHA-1/SHA-512 verification, and installed aliases/projection/supersession/cache lifecycle smoke assertions. Add read-only registry metadata to the unchanged Ubuntu/Windows acceptance matrix; workflow permissions remain contents: read. No publishing credentials or release automation are added.
Validation: local type check, 72 public Markdown files, synthetic API smoke, and 138-file package audit passed. Complete source/compiled/package tests and registry availability must pass in this PR before merge. Cloud registry access is blocked by connect EPERM; existing gh authentication is invalid. npm publication, a tag and GitHub Release remain separate blocked gates. No thresholds or product assertions are weakened.
Local source commit ef2a8c1e059b8c40a72347a685f5fb47c0bef0a9 maps to the remote commit through exact tracked-tree verification; original local history is retained.