2.5.0.0.6 update ci #5071
Merged
2.5.0.0.6 update ci #5071
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
hstove
requested changes
Aug 14, 2024
hstove
approved these changes
Aug 14, 2024
|
🤞 |
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Brings in changes from @BowTiedDevOps which creates the tag and runs the release workflows (pushed to develop, but missing in
masterwhichrelease/2.5.0.0.6is based off of): #4968Modifies the ci workflows to disable building the standalone signer image, and uses a specific branch to create the release binary archives with a hardcode list of binaries (no signer binary).
ex: https://github.com/stacks-network/actions/blob/feat/specific_binaries_stacks-core/stacks-core/create-source-binary/build-scripts/Dockerfile.linux-glibc-arm64#L24
This will create conflicts on a future merge, but it's manageable.