chore(PLA-2124): change how releases work so we do not run into constant checksum issues#5
Merged
jareddellitt merged 1 commit intomainfrom Jan 26, 2026
Merged
Conversation
…ant checksum issues
whatyouhide
approved these changes
Jan 26, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
There was a chicken-and-egg problem here with how artifacts were being built on tag push and needing a checksum file committed based off of those artifacts, which required a force tag. This re-generated the artifacts which caused their hashes to change. I'm switching to just a workflow_dispatch for now so we can tag w/o the artifacts building.