Repository navigation
ci: reuse unchanged browser results across releases - #48
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.
Release browser checks currently rerun the full suite when only the package version changes. Restore a digest-verified coverage receipt from a successful ancestor release, fingerprint each check's actual installed runtime/docs/test inputs, and run only checks without matching historical passes. The final coverage gate accounts separately for online execution, exact local confirmations and inherited online results.
The workflow requires merged docs tooling, preserves build/package/React18+19 hydration/registry gates, and publishes a90-day coverage receipt only after the browser coverage gate succeeds. Original pass provenance and age are preserved; missing, expired or unverifiable history leaves normal checks enabled. force_browser refreshes the non-locally-confirmed suite.
This integrates the corresponding browser reuse tooling in inkrajs/docs; select a merged docs revision containing that tooling for future releases. The first release establishes the baseline because earlier releases have no per-check fingerprints.
Validation: Node24 release-tool tests78 passed; after final workflow changes, targeted release-workflow and restore-baseline tests14 passed. A read-only call against the actual GitHub API confirmed the initial no-baseline fallback. Workflow YAML parsed and git diff --check passed. No full browser suite or npm publication was dispatched for this change.