Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(toolchain)!: bump msrv to 1.67 #361

Merged
merged 2 commits into from
Aug 4, 2023
Merged

Conversation

a-kenji
Copy link
Contributor

@a-kenji a-kenji commented Jul 31, 2023

This updates the msrv to 1.67.

Because an optional dependency of ratatui requires it.

Alternatives: Choose to not bump the versions for optional dependencies, or pin the time version to the latest version that supports 1.65

BREAKING_CHANGE: The msrv is now `1.67`
@TieWay59
Copy link
Contributor

TieWay59 commented Aug 1, 2023

LGTM. Many CI-checks failed on this.

@orhun
Copy link
Member

orhun commented Aug 2, 2023

Hey, what is the exact reason for this bump? i.e. which optional dependency is that? I'm asking because I'm a proponent of avoiding MSRV bump as much as possible.

@a-kenji
Copy link
Contributor Author

a-kenji commented Aug 2, 2023

It is the current reason that the ci for 1.65 fails on some current PR's.

error: package time v0.3.24 cannot be built because it requires rustc 1.67.0 or newer, while the currently active rustc version is 1.65.0

I believe it is the optional calendar feature that pulls this dependency in.

@joshka
Copy link
Member

joshka commented Aug 4, 2023

The N-2 policy change for the time crate is documented at time-rs/time#535.. Having read some of that thread (but not all, it's long), the arguments sound reasonable and I think we shouldn't avoid MSRV bumps.

I'd prefer to avoid the pin time approach (as that probably requires extra manual effort to keep abreast of any CVEs etc.), and so that the only other approach is to remove the calendar widget from the repo. I don't think that's reasonable either.

I'm approving this, but won't merge as I think it's worth hearing @orhun's perspective on this before merging.

Copy link
Member

@orhun orhun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds reasonable, let's bump it up! 🆙

@codecov
Copy link

codecov bot commented Aug 4, 2023

Codecov Report

Merging #361 (b0205e6) into main (440f62f) will increase coverage by 0.23%.
Report is 6 commits behind head on main.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #361      +/-   ##
==========================================
+ Coverage   84.76%   84.99%   +0.23%     
==========================================
  Files          40       40              
  Lines        8603     8686      +83     
==========================================
+ Hits         7292     7383      +91     
+ Misses       1311     1303       -8     

see 2 files with indirect coverage changes

@orhun orhun enabled auto-merge August 4, 2023 17:18
@orhun orhun added this pull request to the merge queue Aug 4, 2023
Merged via the queue into ratatui:main with commit 8cd3205 Aug 4, 2023
@@ -150,7 +150,7 @@ you are interested in working on a PR or issue opened in the previous repository

## Rust version requirements

Since version 0.21.0, The Minimum Supported Rust Version (MSRV) of `ratatui` is 1.65.0.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think "Since version 0.21.0" should be updated to 0.23.0 as the MSRV will be bumped in the next release.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, right. Feel free to submit a PR!

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done at #369 :)

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.

6 participants