Repository navigation
Prepare RefMint 1.0 release channels, support and exact archive checks - #13
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.
Prepares an unpublished 1.0.0 candidate after #12, retaining the runtime, v1 format and historical compatibility fixtures.
latest, alpha usesalpha, beta/RC usesbeta; validate both source and installed manifests, with negative tests.pnpm test:package /absolute/path/to/archive.tgzqualify the supplied archive without rebuilding, including alpha.3/beta.2 compatibility, and report SHA-256/SHA-512. Measurement history remains explicitly carried forward.Validation on Node 26.13.0/macOS ARM: 42 tests, TypeScript, 21 installed compatibility tests, demo/comparison/workflow checks, ordinary package check and exact-archive check passed. A deliberately wrong-channel archive is rejected. npm dry-run passed; it did not publish anything. The supplied-archive origin guard was also checked with a controlled archive that rewrites its own runtime hashes: it passed before the guard and is rejected afterward. Exact-archive validation and npm dry-run passed again.
All 7 CI checks passed on
9ec8844: Node 22/24/26 Linux, Node 24 Windows/macOS, Chromium/Firefox/WebKit and PDF extraction/lookup.No npm tags, Billetsys dependency or runtime API changed. Publication and consumer rollout require separate decisions; the 1.0.0 manifest identifies a candidate, not an already published version.