Add package validation workflow. #144
Merged
Conversation
This file contains 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
|
…tch package renames in beta distros.
|
I know, I'm fixing it :P I also decided to just put it into the canary job, since splitting it up into the part that tests package installation on LTS versions (for use in validating changes in PRs) and the part that tests package installation on betas (to catch package renames) felt like more trouble than it was worth to avoid a tiny amount of GHA compute. |
goffrie
approved these changes
Apr 18, 2024
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.
Summary
Having a job that regularly creates the packages and installs them using each distro's package manager is important for making sure we catch things like deprecated options and package renames as quickly as possible.
Test plan
The action running on this PR.