Automate MSRV fixes

Open
#42 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions, rust
Domain
build-system, ci-cd

Research direction

Locate the workflow that runs cargo msrv verify and the check-lurk-compiles workflow. Read how their failures and current version are handled, then determine the repository’s expected approach for opening or updating a fix PR. Done means the MSRV fix is automated on failure and the relevant compile-check workflow also runs the MSRV check.

Written by the indexing model from the issue text.

Description

Currently, the MSRV check runs cargo msrv verify and fails if the MSRV is not up to date. This requires the user to run cargo msrv locally and then update/submit a PR with the fix.

This can be automated by having the workflow run cargo msrv --min <CURRENT_VERSION> on a failure, and then automatically opening/updating a PR with the new MSRV fix.

To prevent similar breakages from occurring downstream, we could also run the MSRV check in the check-lurk-compiles workflow.

Dominant language
No language data
Stars
0
Forks
3
Avg merge
59m
Merged PRs (30d)
2

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from argumentcomputer/ci-workflows

All issues in argumentcomputer/ci-workflows

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.