axodotdev / axodotdev/cargo-dist
[Feature] Version the generated CI scripts
- Dominant language
- Rust
- Stars
- 2.1k
- Forks
- 149
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 32
Description
I think it would be a smart move to version the generated CI scripts (using a comment or something at the top of the file). Such that each time the CI runs it can have a quick job to check what the latest version is and fail if the major or minor version number has increased. Of course this would only fail the specific CI job and would still correctly release everything.
Versioning the CI scripts will ensure that the CI is kept updated as changes to the tool are made. Additionally this check could be easily removed as one would just need to remove the update-check job.
Contributor guide
Research direction
Start by locating where the generated CI scripts are assembled and how the CI workflow runs them. Determine how a script version would be recorded and compared with the current tool version, then verify that only the update-check job fails when a major or minor version is newer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100