feat: Update release tools#5
Merged
Merged
Conversation
|
✔️ b808608 - Conventional commits check succeeded. |
WalkthroughVersion updates for CI/CD tools in GitHub Actions workflows. Four tools updated in the prepare-release workflow (git-cliff, cargo-workspaces, cargo-semver-checks, holochain_release_util), and two tools updated in the publish-release workflow (cargo-workspaces, holochain_release_util). No logic or control flow changes. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.github/workflows/prepare-release.yml:
- Line 36: The workflow refers to a non-existent crate identifier
holochain_release_util@0.1.4 which will make the job fail; open the
prepare-release.yml job that installs tools and replace or remove the invalid
entry holochain_release_util@0.1.4 — either update it to the correct published
crate name/version (or the correct registry) or omit it and add only known-valid
tools (e.g., git-cliff@2.12.0, cargo-workspaces@0.4.2,
cargo-semver-checks@0.46.0); ensure the final list contains only crates that
exist on crates.io.
In @.github/workflows/publish-release.yml:
- Line 22: The workflow references a non-existent crate version
holochain_release_util@0.1.4 which will break CI; open publish-release.yml (and
verify prepare-release.yml for consistency), confirm the correct
holochain_release_util version on crates.io, then update the reference in the
workflow to that published version (or publish the missing
holochain_release_util@0.1.4 before merging) and ensure the tool line
cargo-workspaces@0.4.2 remains correct and consistent across both files.
jost-s
approved these changes
Feb 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See holochain/release-integration#25 and https://github.com/holochain/release-integration/releases/tag/v0.1.4
Summary by CodeRabbit