Repository navigation
ci: automated release gate (tests, byte budget, real-browser inscription path) - #5
Merged
Merged
Conversation
- scripts/gate.mjs: tests, pinned minification, tests against the minified artifact, byte budget against the live inscription body, browser smoke, and a printed release record (bytes, sha256, dependency inscription IDs) - scripts/browser-smoke.mjs: real Chromium loading the library through /content/<id> against a stub ord server, asserting the 1 MiB round-trip, the empty-sat path making no /content/null request, and the decoder inscription loading lazily exactly once - package.json/.gitignore: dev-only tooling, nothing inscribed - CI runs the same gate on push and pull request
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.
Answers "can the release gate be automated": mostly yes. This adds the checks a machine can run, and states plainly the ones it cannot.
What runs
node scripts/gate.mjs, also wired to CI on push and pull request:/content/<id>against a stub ord serverThe browser stage asserts what a unit test cannot: the recursive
<script src="/content/<id>">load definesOrdJS, a 1 MiB image round-trips byte-exactly through realfetch/btoa, the empty sat makes no/content/nullrequest at the network level, and the decoder inscription is fetched lazily and exactly once across two concurrent calls.Current output
Release record for the current head: 3,004 B artifact, sha256
080e80c2…7918e7bb, minifierbun 1.3.14 build --no-bundle --minify-syntax --minify-whitespace --target=browser, dependency inscriptiona9f6a9b0…308566i0.Verified the gate actually fails
Two mutants against the current source. Wrapping the class in an IIFE so it never reaches the global scope: 3 stages fail, including the browser stage with the class undefined. Raising the base64 chunk size to 256 KiB: the 1 MiB round-trip fails in both the suite and the browser. A gate that cannot fail is decoration.
What is still manual
Printed by the gate itself, so it cannot be forgotten: a real ord server with the sat index enabled and disabled, Firefox and WebKit, and a commit/reveal fee dry-run at the chosen rate. CI cannot honestly cover those.
Nothing here is inscribed —
package.json,scripts/, CI and tests are repository-only. The released artifact remains a minifiedsrc/content/OrdJS.js.