Skip to content

ci: build artifacts after release-plz publishes#102

Merged
garritfra merged 1 commit into
mainfrom
ci/build-release-artifacts-after-release-plz
May 4, 2026
Merged

ci: build artifacts after release-plz publishes#102
garritfra merged 1 commit into
mainfrom
ci/build-release-artifacts-after-release-plz

Conversation

@garritfra
Copy link
Copy Markdown
Owner

Summary

  • Fix the release handoff by using release-plz outputs to build and upload artifacts in the same release.yml run after crates.io publishing succeeds.
  • Add workflow_dispatch with a tag input so the existing draft v0.5.0 release can be repaired without moving tags.
  • Update release docs to describe the same-run artifact path and recovery flow.

Root cause

release-plz created v0.5.0 with GITHUB_TOKEN. GitHub does not trigger a new workflow run from tag pushes created by GITHUB_TOKEN, so the tag-gated build/upload jobs never ran.

Test plan

  • ruby -e 'require "yaml"; YAML.load_file(".github/workflows/release.yml"); puts "release.yml yaml ok"'
  • python3 -c 'import tomllib; tomllib.load(open("release-plz.toml", "rb")); print("release-plz.toml ok")'
  • cargo fmt --all --check && cargo clippy --workspace --all-targets --all-features && cargo test

Made with Cursor

Use release-plz outputs to continue artifact builds in the same trusted release workflow because tags created with GITHUB_TOKEN do not trigger a second workflow run.

Co-authored-by: Cursor <cursoragent@cursor.com>
@garritfra garritfra merged commit 7efe4b8 into main May 4, 2026
10 checks passed
@garritfra garritfra deleted the ci/build-release-artifacts-after-release-plz branch May 4, 2026 10:27
@github-actions github-actions Bot mentioned this pull request May 4, 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.

1 participant