Skip to content

fix(release): replace release-plz with release-please - #170

Merged
Teakowa merged 1 commit into
mainfrom
agent/wright-169-release-please
Aug 18, 2026
Merged

fix(release): replace release-plz with release-please#170
Teakowa merged 1 commit into
mainfrom
agent/wright-169-release-please

Conversation

@Teakowa

@Teakowa Teakowa commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

Summary

  • replace the failed release-plz integration with a root-level release-please product release flow;
  • maintain one Wright Release PR using version.txt and CHANGELOG.md;
  • synchronize Cargo workspace versions, Cargo.lock, and checked-in dist/ metadata;
  • preserve the existing release gates, native artifacts, npm/GitHub Packages, and package-manager publication pipeline;
  • keep the built-in Actions token for release management and reserve secrets.GH_TOKEN for the cross-repository Homebrew tap.

Why

release-plz attempted to package historical internal workspace dependencies while maintaining the Release PR. Wright is a single product implemented as a non-publishable Cargo workspace, so release automation must not require internal crates to become crates.io packages.

Validation

  • python3 scripts/sync-release-version.py --version 0.2.4
  • python3 scripts/verify-dist.py
  • cargo metadata --locked --no-deps --format-version 1
  • JSON/YAML workflow parsing
  • git diff --check

The real post-merge Release PR and release cycle remain to be verified by GitHub Actions.

Fixes #169

@Teakowa
Teakowa marked this pull request as ready for review August 18, 2026 09:40
@Teakowa
Teakowa merged commit 2f6c572 into main Aug 18, 2026
13 checks passed
@Teakowa
Teakowa deleted the agent/wright-169-release-please branch August 18, 2026 10:14
@github-project-automation github-project-automation Bot moved this from Backlog to Done in Make Workshop Great Again Aug 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Development

Successfully merging this pull request may close these issues.

Replace release-plz with a Release-PR-driven product release flow

1 participant