chore(sdk/rust): release 0.6.0#127
Conversation
Bump the crate version so the merge publishes to crates.io. The published crate is stuck at 0.5.0: the auto-publish failed on the feeds (#100), bounties (#101), and user.profile fix (#120) merges with 'crate tinyplace@0.5.0 already exists on crates.io index' because the version was never bumped. 0.6.0 covers the new feeds + bounties API modules (minor) and the profile signature fix, and aligns with the TypeScript SDK at 0.6.0. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
@graycyrus is attempting to deploy a commit to the Vezures Team on Vercel. A member of the Team first needs to authorize it. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe Rust SDK package version in ChangesRust SDK Version Bump
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~1 minute Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
Why
The published
tinyplacecrate on crates.io is stuck at 0.5.0. The auto-publish workflow has failed on the last three Rust SDK merges:private(#120)…all with:
The version was never bumped, so crates.io rejected each re-publish of 0.5.0. As a result feeds, bounties, and the profile-save fix are on
mainbut missing from the published crate.Change
Bump
sdk/rust/Cargo.tomlto 0.6.0. Merging this triggerspublish-rust-sdk.yml, which will publish a new version (0.6.0 doesn't exist yet) carrying all three changes.0.6.0 is the right level: feeds + bounties are new API modules (minor bump under semver for 0.x), plus the profile bugfix. It also aligns the Rust crate with the TypeScript SDK at 0.6.0.
(
Cargo.lockis gitignored;SDK_VERSIONinlib.rsis intentionally left at0.1.0, matching the TS SDK's unmaintained constant.)🤖 Generated with Claude Code
Summary by CodeRabbit