-
Notifications
You must be signed in to change notification settings - Fork 30
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
Validate tags in CI #135
Comments
Closed
CI already does that:
That can probably be extended. |
hasufell
added a commit
that referenced
this issue
Oct 1, 2023
hasufell
added a commit
that referenced
this issue
Oct 1, 2023
hasufell
added a commit
that referenced
this issue
Oct 1, 2023
hasufell
added a commit
that referenced
this issue
Oct 1, 2023
hasufell
added a commit
that referenced
this issue
Oct 1, 2023
Done: #137 Example pipeline on prereleases: https://github.com/haskell/ghcup-metadata/actions/runs/6369219389/job/17289264412#step:10:18 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently it's very easy to overlook or otherwise mess up the tags when adding a new tool version. CI should ideally perform some consistency checks to catch this failure mode:
Latest
and oneLatestPrerelease
, and oneRecommended
version for each toolghc
tool should have abase-...
tagThe text was updated successfully, but these errors were encountered: