ci: use shared release tools#130
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (4)
💤 Files with no reviewable changes (2)
📝 WalkthroughWalkthroughThe release workflow now conditionally provisions a Nix environment and invokes x52 release tools using release-plz JSON environment variables. The default Nix devshell includes the release-tools package, replacing the removed repository scripts. ChangesRelease tooling migration
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 Checkov (3.3.8).github/workflows/release.ymlTraceback (most recent call last): Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
x52dev/nixflake input and exposex52-release-toolsin the default development shellWhy
The release helpers now live in
x52dev/nix, where their dependencies, fixes, and regression tests can be maintained once. Contracts already consumes that flake, so its release job can use the shared package without retaining duplicate scripts.Release behavior is unchanged: release-plz still runs first with the existing crates.io authentication, changelog updates still run only for created PRs, and release-note updates still run only for created releases.
Validation
nix develop -c just fmtnix develop -c just checknix develop -c just test(35 nextest tests and 12 doctests passed; rustdoc completed with warnings denied)x52-bump-changelogsandx52-update-release-notesare both available in the default development shellSummary by CodeRabbit