Repository navigation
fix(ci): verify published beta integrity and wait for registry propagation - #74
Merged
Merged
Conversation
Contributor
Playwright test results
Details
|
Contributor
|
📊 Ionic 9 Playwright Test Report View the detailed Ionic 9 report: https://webview-native-ui.github.io/ionic-theme-md3/pr-74/ Ionic 8 runs against the same screenshots in a separate matrix job. View both results in the workflow run. |
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.
Duplicate beta release jobs can receive npm E409 while a successful publication is still propagating. Once visible, npm may return
dist.integrityas a singleton JSON array. The existing string comparison rejects the matching archive and leaves the release run failed.Accept the matching digest as either a string or exactly one array entry. Mismatched and ambiguous responses continue to fail. Extend E409 metadata checks to a bounded five minutes without repeating npm publish.
Add seven regression tests that execute the workflow's actual publication logic with a fake registry and timers. They cover matching archives, malformed responses, delayed visibility, the five-minute bound, other errors and immediate integrity mismatch failures. Run these through the existing ESM CI entry point. Build, lint and the full ESM checks passed. The public beta archive matches its immutable CI artifact by SHA-512.