Skip to content

docs(changelog): record the MSRV bump to 1.64.0 in 0.5.0#877

Open
ameyypawar wants to merge 1 commit into
tower-rs:masterfrom
ameyypawar:fix/changelog-msrv-1.64
Open

docs(changelog): record the MSRV bump to 1.64.0 in 0.5.0#877
ameyypawar wants to merge 1 commit into
tower-rs:masterfrom
ameyypawar:fix/changelog-msrv-1.64

Conversation

@ameyypawar

Copy link
Copy Markdown
Contributor

Summary

Fixes #785.

tower/Cargo.toml has rust-version = "1.64.0", but the CHANGELOG's last MSRV note (in the 0.5.0 section) only records the bump to 1.63.0 from #741.

Tracing the history, the 1.64.0 bump happened in the same 0.5.0 cycle but went undocumented: #741 raised MSRV to 1.63.0, and then #778 ("use workspace dependencies", commit 85080a5) raised rust-version to 1.64.0. That commit is contained in the tower-0.5.0 tag, and rust-version has stayed at 1.64.0 ever since.

This adds the missing entry to the 0.5.0 changelog (keeping the existing #741/1.63.0 line, since both bumps really happened that cycle):

  - **MSRV**: Increase MSRV to 1.63.0 ([#741])
+ - **MSRV**: Increase MSRV to 1.64.0 ([#778])

plus the corresponding [#778] link reference. CHANGELOG-only change.

(For reference, #792 — "relax MSRV to 1.63" — was closed without merging, so documenting 1.64.0 matches the intended MSRV rather than reverting it.)

The 0.5.0 changelog documents only tower-rs#741's bump to 1.63.0, but tower-rs#778
("use workspace dependencies") raised `rust-version` to 1.64.0 in the same
release cycle (it ships in tower-0.5.0). `tower/Cargo.toml` has read 1.64.0
ever since while the changelog still recorded 1.63.0.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Changelog says that MSRV is 1.63 but it's 1.64

1 participant