Repository navigation
fix(ci): backport npm publisher checks to v3 - #234
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.
What does this change?
Backport the release authentication and publication checks to the stable v3 workflow. Verify npm OIDC token exchange for all packages before publishing and wait for every expected npm version to be available before creating a GitHub release.
Target branch
Changeset
Upstream PRs
Verification
yarn lintandyarn testpassed.3.2.0versions against the public npm registry.actionlint .github/workflows/release.ymlpassed.Example E2E · e2e SDK
Commit: 17c01ff · CI run
Time includes SDK startup and app installation; excludes device preparation and builds.