Skip to content

Retry artifact uploads and report failed tag releases - #39

Merged
ddehilster merged 1 commit into
mainfrom
ci/publish-failure-visibility
Sep 26, 2026
Merged

ddehilster merged 1 commit into
mainfrom
ci/publish-failure-visibility

Conversation

@ddehilster

Copy link
Copy Markdown
Member

Why

NLPPlus v2.2.39 (engine v4.2.0) never reached PyPI. The Linux wheel job built every wheel, then GitHub returned Failed to FinalizeArtifact ... (403) Forbidden. Because upload_pypi and Make release need every build job, both were skipped. Nothing reported the failure for five days. The Update nlp-engine & publish run had succeeded, so the release looked shipped. v2.2.37 hit the same kind of failure once before.

What

  • Retry uploads: each upload-artifact step now runs with continue-on-error. If it fails, a second attempt runs with overwrite: true. A failed retry still fails the job.
  • Report failures: a new notify_failure job runs on v* tags when any job fails. It opens an issue in this repo naming the tag and linking the run, with a pointer to Re-run failed jobs.

PR and workflow_dispatch runs are unaffected: the notice job only runs on tags.

The v2.2.39 run itself (35643462731) is being re-run separately. This PR prevents the next silent failure.

Refs #38, VisualText/nlp-engine#744

🤖 Generated with Claude Code

v2.2.39 (engine v4.2.0) never reached PyPI: the Linux wheel job built
every wheel, then GitHub rejected the artifact finalize with a 403, so
upload_pypi and the release were skipped. Nothing reported it, and the
successful "Update nlp-engine & publish" run made it look shipped.

- Retry each upload-artifact step once (overwrite: true).
- On a v* tag, if any job fails, open an issue linking the run.

Refs #38, VisualText/nlp-engine#744

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ddehilster
ddehilster merged commit e64e02f into main Sep 26, 2026
5 checks passed
@ddehilster
ddehilster deleted the ci/publish-failure-visibility branch September 26, 2026 22:03
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.

1 participant