Skip to content

fix(ci): retry pkg-pr-new publish on transient failures#469

Closed
antfubot wants to merge 1 commit into
mainfrom
fix/retry-pkg-pr-new-publish
Closed

fix(ci): retry pkg-pr-new publish on transient failures#469
antfubot wants to merge 1 commit into
mainfrom
fix/retry-pkg-pr-new-publish

Conversation

@antfubot

Copy link
Copy Markdown
Collaborator

Description

The "Release Commit" check has been intermittently failing on open PRs (e.g. #465, #468) with:

Check failed (404): {"url":"/check","statusCode":404,"statusMessage":"Not Found","message":"There is no workflow defined for ...","stack":""}

This is a known transient issue in the external pkg-pr-new continuous-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 the push-triggered run) succeeds without any code change, confirming the failure is external and non-deterministic.

This PR wraps the pkg-pr-new publish step 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.

@pkg-pr-new

pkg-pr-new Bot commented Jul 23, 2026

Copy link
Copy Markdown

Open in StackBlitz

@vitejs/devtools

npm i https://pkg.pr.new/@vitejs/devtools@469

@vitejs/devtools-kit

npm i https://pkg.pr.new/@vitejs/devtools-kit@469

@vitejs/devtools-oxc

npm i https://pkg.pr.new/@vitejs/devtools-oxc@469

@vitejs/devtools-rolldown

npm i https://pkg.pr.new/@vitejs/devtools-rolldown@469

@vitejs/devtools-vite

npm i https://pkg.pr.new/@vitejs/devtools-vite@469

@vitejs/devtools-vitest

npm i https://pkg.pr.new/@vitejs/devtools-vitest@469

commit: 189b3be

@antfu antfu closed this Jul 23, 2026
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.

2 participants