Switch release-plz workflow back to upstream action once PR #2789 merges
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 35
- Forks
- 4
- Avg merge
- 17h 19m
- Merged PRs (30d)
- 8
Description
Background
In commit a4d343a6 we replaced release-plz/action@v0.5 with a custom workflow that installs release-plz from a fork pinned to PR release-plz#2789 (commit e8ca8da97dc8f472820a67eece651604887b1c7d on structured-world/release-plz).
This was necessary because upstream release-plz 0.3.157 (latest as of 2026-05) crashes the release-pr job with "no matching package named X found, location searched: crates.io index". Root cause: cargo package's prepare_for_upload step queries crates.io for every dep, which fails for our publish = false internal libs (right-core, right-db, right-mcp, right-codegen, right-memory). This is upstream issue release-plz#2595 — Case 2/B.
PR #2789 fixes this by falling back to source-directory comparison when cargo package fails in git_only mode. Multiple users in the PR thread confirmed the fork branch works for their monorepos. The PR has been open since 2026-04-12 with all CI checks passing, awaiting maintainer review.
Cost of the workaround
- Each release-plz workflow run compiles release-plz from source. ~5-8 min with
Swatinem/rust-cache, longer cold. - Supply-chain expansion: a third-party fork pinned to a SHA. Mitigated by SHA pinning, but still a maintenance trap.
- Lost the action's output parsing (PR URLs etc.). Not consumed downstream, so harmless today.
Definition of done
When release-plz#2789 merges and a release-plz version containing the fix ships (and release-plz/action releases a new tag bundling that version):
- Revert
.github/workflows/release-plz.ymlto userelease-plz/action@<new-version>with the per-stepenv: GITHUB_TOKEN: ${{ secrets.GH_RELEASE_TOKEN }}. - Verify both
Release-plz releaseandRelease-plz PRjobs still pass on a real push. - Verify humanize-changelog still triggers on the release PR (filter uses
head.refprefix inhumanize-changelog.yml, should still work). - Close this issue.
Watch list
- release-plz#2789 — the actual fix.
- release-plz#2595 — tracking issue.
- release-plz/action releases — for the version bump that includes the fixed release-plz.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Wait for release-plz#2789 and a release-plz/action tag containing its fix, then inspect .github/workflows/release-plz.yml and the head.ref filter in humanize-changelog.yml. Restore the upstream action with the per-step token environment, verify both release and PR jobs on a real push, and confirm humanize-changelog still triggers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust
- Domain
- ci-cd, release
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 38/100