chore: bump version to 0.6.0 and fix repository URLs#178
Conversation
v0.5.0 was already released on Mar 5, 2025. Bump to 0.6.0 so release-plz can create a proper release for the changes since then. Also update repository and homepage URLs from aurora-is-near to Near-One.
There was a problem hiding this comment.
Pull request overview
Bumps the workspace crate version to avoid release-plz attempting to re-release an already-published version, and updates the workspace-level repository metadata to point at the new GitHub org.
Changes:
- Bump
[workspace.package].versionfrom0.5.0to0.6.0. - Update
[workspace.package]repositoryandhomepageURLs tohttps://github.com/Near-One/near-plugins.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| repository = "https://github.com/Near-One/near-plugins" | ||
| homepage = "https://github.com/Near-One/near-plugins" |
There was a problem hiding this comment.
repository/homepage were updated under [workspace.package], but the member crates (near-plugins, near-plugins-derive) don’t currently inherit these fields (their Cargo.toml only has authors/edition/rust-version/version.workspace = true). As a result, the published crate metadata will still be missing/unchanged. Consider adding repository.workspace = true and homepage.workspace = true (and any other shared metadata you want) in each crate’s [package] section, or set the URLs directly per crate.
Add repository, homepage, description, license, readme, and keywords inheritance so the published crate metadata is correct on crates.io.
Summary
repositoryandhomepageURLs fromaurora-is-neartoNear-OneNotes
Once merged, release-plz will create a fresh release PR for 0.6.0 with a proper changelog diff from v0.5.0. The
CARGO_REGISTRY_TOKENsecret still needs to be configured before the actual publish will work.