ci: remove dependabot + gomod, always fetch latest #1293
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
Instead of using Dependabot to test, this always fetches the latest TSA build. I'm not positive this is a great idea, however. Signed-off-by: William Woodruff <[email protected]>
Signed-off-by: William Woodruff <[email protected]>
jku
approved these changes
Feb 10, 2025
|
hmm, looks like my approval is still valid after updating. I'll merge. |
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.
Instead of using Dependabot to test for an update (which was unreliable, per #1288), this always fetches the latest TSA build.
I'm not positive this is a great idea, however -- an alternative that doesn't involve blindly pulling the latest release would be to set up a release-tracking workflow that files an issue for us whenever a new TSA release is made. That would be slightly more manual, but would also avoid opaque CI changes.