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

Update GitHub Actions #1263

Merged
merged 3 commits into from Nov 10, 2022
Merged

Update GitHub Actions #1263

merged 3 commits into from Nov 10, 2022

Conversation

dhardy
Copy link
Member

@dhardy dhardy commented Nov 10, 2022

... plus a couple of minor things

@newpavlov
Copy link
Member

I wouldn't say that bumping MSRV to 1.51 is a "minor thing".

@dhardy
Copy link
Member Author

dhardy commented Nov 10, 2022

The actual bump was already merged: #1246.

Copy link
Member

@newpavlov newpavlov left a comment

Choose a reason for hiding this comment

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

Personally, I think 1.51 could be a bit too steep for a crate like rand. With bump to 1.38 we could shift responsibility to crossbeam, it's much less impactful, and it's easier to pin one crate to preserve the old MSRV, than a number of affected rand crates. Be prepared to the same reaction as we've seen for once_cell, if not worse.

But I guess, it's too late to raise such concerns...

@dhardy
Copy link
Member Author

dhardy commented Nov 10, 2022

The next Rand release will be a breaking release. once_cell had a major bump in a non-breaking release.

Given that, and that 1.51 is likely to be two years old by the time Rand 0.9 releases (or more, we're not exactly making rapid progress on it), I don't think this is an issue.

@dhardy dhardy merged commit 9720f11 into master Nov 10, 2022
@newpavlov
Copy link
Member

newpavlov commented Nov 10, 2022

Ah, if MSRV bump will be done as part of v0.9, then I have no objections. It could be even worth to bump to 1.56 for edition update.

@dhardy
Copy link
Member Author

dhardy commented Nov 10, 2022

👍

The gh-pages deployment needs fixing :-(

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.

None yet

2 participants