feat: build and attach Start9 s9pk packages on each release tag#644
Open
CyberAshven wants to merge 2 commits into
Open
feat: build and attach Start9 s9pk packages on each release tag#644CyberAshven wants to merge 2 commits into
CyberAshven wants to merge 2 commits into
Conversation
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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.
Adds
.github/workflows/trigger-start9-build.ymlOn every
v*tag push or published release:BitcoinCash1/bitcoin-cash-daemon-startos, auto-bumps the version files to match the new tag, and builds all 3 architecture.s9pkpackages (x86_64, aarch64, riscv64)GITHUB_TOKENrepository_dispatchtoBitcoinCash1/bitcoin-cash-daemon-startosso they can publish a signed copy for the Start9 marketplace (requiresSTART9_BUILD_TOKENsecret would be skipped if there is none)A concurrency group on the tag name prevents duplicate builds if both the tag push and release publish fire for the same version.