Repository navigation
ci: retry a failed registry release by hand - #32
Merged
Merged
Conversation
A failed registry release cannot be re-run: the release service keys uploaded artifacts by workflow run ID, so a rerun's new attestation conflicts with the first attempt's (INVALID_REQUEST: Artifact upload is invalid, run 37486660259 attempt 2). Starting emdash-release.yml by hand would work, but the registry keeps one workflow connection per package, and approving one for emdash-release.yml replaces the connection for release.yml, so the next normal release would need another approval. release.yml now also runs on workflow_dispatch. On main it skips npm and calls emdash-release.yml with the version from package.json, so the run still comes from release.yml on refs/heads/main and matches the existing connection. No changeset: the package does not change.
|
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
1 participant
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.
Lets a failed registry release be retried by hand without publishing a new npm version and without replacing the registry's workflow connection.
A failed registry release cannot be re-run. The release service keys uploaded artifacts by workflow run ID, so a rerun's new attestation conflicts with the first attempt's: rerunning the 0.3.1 publish job failed with
INVALID_REQUEST: Artifact upload is invalid(run 37486660259, attempt 2). Startingemdash-release.ymlby hand gets a new run, but the registry keeps one workflow connection per package, so approving one foremdash-release.ymlreplaces the connection forrelease.yml, and the next normal release would ask for approval again.Changes
release.ymlalso runs onworkflow_dispatch. Started by hand onmain, it skips the Changesets and npm jobs and callsemdash-release.ymlwith the name and version frompackage.json, in the samepublished-packagesformat Changesets produces. The run still comes fromrelease.ymlonrefs/heads/main, so it matches the existing connection.emdash-release.ymlby hand.No changeset: the package does not change.
Verified
pushthe jobs are unchanged, onworkflow_dispatchonlyregistry-retry-versionandregistry-retryrun.jq -c '[{name, version}]' package.jsongives[{"name":"@eisbachcode/emdash-plugin-analytics","version":"0.3.1"}], the same string the 0.3.1 run passed torelease plan.workflowConnectionPolicyMatchescompares repository, IDs, workflow file, refs and environments), not observed.