fix(ci): retry pkg-pr-new publish on transient failures#469
Closed
antfubot wants to merge 1 commit into
Closed
Conversation
@vitejs/devtools
@vitejs/devtools-kit
@vitejs/devtools-oxc
@vitejs/devtools-rolldown
@vitejs/devtools-vite
@vitejs/devtools-vitest
commit: |
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.
Description
The "Release Commit" check has been intermittently failing on open PRs (e.g. #465, #468) with:
This is a known transient issue in the external
pkg-pr-newcontinuous-release service (see stackblitz-labs/pkg.pr.new#95, #147, #316, #413) — not a problem with this repo's build. Re-running the same commit (e.g. via thepush-triggered run) succeeds without any code change, confirming the failure is external and non-deterministic.This PR wraps the
pkg-pr-new publishstep in a retry loop (3 attempts, backoff) so a transient hiccup from the third-party service no longer fails the "Release Commit" check.Linked Issues
Additional context
Verified the workflow YAML is syntactically valid; no other CI workflows were affected.
This PR was created with the help of an agent.