Skip to content

ci: reuse unchanged browser results across releases - #48

Merged
NWYLZW merged 1 commit into
mainfrom
feat/browser-result-reuse
Oct 29, 2026
Merged

NWYLZW merged 1 commit into
mainfrom
feat/browser-result-reuse

Conversation

@NWYLZW

@NWYLZW NWYLZW commented Oct 29, 2026

Copy link
Copy Markdown
Contributor

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.

@NWYLZW
NWYLZW merged commit 7891ce3 into main Oct 29, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant