fix(rust): Add cargo publish step to release workflow#32
Merged
Conversation
Adding CLAUDE.md with task information for AI processing. This file will be removed when the task is complete. Issue: #31
The release workflow was correctly detecting that the package was not published to crates.io, but was missing the actual `cargo publish` step. Changes: - Add publish-crate.mjs script to handle crates.io publishing - Add rust-paths.mjs helper for multi-language repository support - Update rust.yml workflow to include publish step in both auto-release and manual-release jobs - Add case study documentation for issue #31 The workflow now: 1. Builds the release binary 2. Publishes to crates.io (NEW) 3. Creates GitHub release Fixes #31 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Member
Author
🤖 Solution Draft LogThis log file contains the complete execution trace of the AI solution draft process. 💰 Cost estimation:
Now working session is ended, feel free to review and add any feedback on the solution draft. |
This was referenced Jan 18, 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
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.
Summary
This PR fixes the missing crates.io publishing step in the Rust release workflow.
Problem
The release workflow correctly detected that version 0.4.0 was not published to crates.io:
However, the workflow only:
cargo build --release)The actual
cargo publishstep was missing, so the package was never published to crates.io.Solution
Added the missing
Publish to Crates.iostep to bothauto-releaseandmanual-releasejobs in the workflow, following best practices from the template repository.Changes
rust/scripts/publish-crate.mjs: New script to handle crates.io publishingrust/scripts/rust-paths.mjs: Helper module for multi-language repo support.github/workflows/rust.yml: Added Publish to Crates.io stepdocs/case-studies/issue-31/: Case study documentationRepository Secret Requirements
The repository needs
CARGO_REGISTRY_TOKENsecret configured for crates.io authentication.Test Plan
Related Issues
References
Fixes #31
🤖 Generated with Claude Code