chore: release 0.5.1#182
Conversation
Downgrade version from 0.6.0 to 0.5.1 — the 0.6.0 was never published to crates.io or tagged, so we can safely step it back. As discussed, the changes since v0.5.0 (syn 2.0, edition 2024, dep bumps) are purely internal and don't affect the public API or storage layout, so a patch release is more appropriate.
There was a problem hiding this comment.
Pull request overview
This PR prepares the repository for a v0.5.1 patch release by reverting the previously bumped workspace version (0.6.0 → 0.5.1) and documenting the release in the changelog, aligning with the fact that 0.6.0 was never published.
Changes:
- Downgrade workspace package version from
0.6.0to0.5.1. - Add a
0.5.1section toCHANGELOG.mddescribing dependency/tooling updates.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
Cargo.toml |
Sets [workspace.package].version to 0.5.1 so all workspace crates inherit the patch version. |
CHANGELOG.md |
Adds a new 0.5.1 release entry documenting internal dependency and tooling changes. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| @@ -1,3 +1,19 @@ | |||
| # 0.5.1 | |||
There was a problem hiding this comment.
The changelog’s version headings elsewhere include a date or “(TBD)” (e.g., “# 0.3.0 (TBD)”, “# 0.1.0 (2023-05-08)”), but the new “# 0.5.1” entry doesn’t. For consistency/readability, consider adding the release date (or the same parenthetical convention used in other sections).
| # 0.5.1 | |
| # 0.5.1 (TBD) |
| - Updated `darling` from 0.13 to >=0.20. | ||
| - Updated `near-sdk` from >=5.2 to 5.25. | ||
| - Updated `near-workspaces` from 0.14 to 0.22. |
There was a problem hiding this comment.
Some dependency upgrade bullets use non-specific version ranges (e.g., “from >=5.2 to 5.25”, “from 0.13 to >=0.20”), which is ambiguous in a changelog. It would be clearer to state concrete previous→new versions, or reflect the actual constraints used in Cargo.toml (e.g., darling is constrained to ">=0.20, <0.21").
| # 0.3.0 (TBD) | ||
|
|
||
| ## BREAKING CHANGES: |
There was a problem hiding this comment.
After the new 0.5.1 section, the next section is “# 0.3.0 (TBD)”. Having lower-version “(TBD)” sections beneath a released 0.5.x entry makes the changelog ordering confusing. Consider reorganizing into an “Unreleased” section and/or adding the missing 0.4.x/0.5.0 entries so versions are listed in descending order.
Summary
The 0.6.0 bump was merged in #178 but never actually published — the crates.io release failed due to a missing
CARGO_REGISTRY_TOKEN, and no git tag or GitHub release was created. So we can safely step the version back.The changes since v0.5.0 (syn 1→2, edition 2024, dep bumps) are purely internal — no public API changes, no storage layout changes. A patch release better reflects that and avoids signaling a breaking change to consumers who depend on near-plugins for on-chain state management.
Context
https://nearone.slack.com/archives/C0A64SAMDNG/p1774500315405309?thread_ts=1774500315.405309