ci: move MSRV check from PR CI to release workflows #1509
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The MSRV check now only runs on push to main/next (in publish-dry-run.yml) and when publishing a release (in publish-main.yml), rather than on every PR. This makes PR CI faster and less resource-intensive. Any MSRV issues will still be caught before publication, and can be fixed locally using scripts/check-msrv.sh. Changes: - Delete .github/workflows/msrv.yml - Add cleanup-runner action for freeing disk space - Add MSRV check steps to publish-dry-run.yml - Add MSRV check steps to publish-main.yml See also: - 0xMiden/miden-base#2233 - 0xMiden/miden-vm#2468 - 0xMiden/miden-vm#2460
huitseeker
added
the
no changelog
Mirko-von-Leipzig
approved these changes
Jan 13, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The MSRV check now only runs on push to main/next (in publish-dry-run.yml) and when publishing a release (in publish-main.yml), rather than on every PR.
This makes PR CI faster and less resource-intensive. Any MSRV issues will still be caught before publication, and can be fixed locally using scripts/check-msrv.sh.
See also: