The aim of this PR is to create a signer release every time there is a core release happening, with the tag set as <core_release>.0.
This PR also moves most of the release workflow out of stacks-core and into actions repository such that on subsequent changes to the release process, we can easier adjust the workflows without the need of as many stacks-core pull requests.
I've also implemented latest docker image tags on non-RC releases and removed the signer- word from the signer version tag as it was redundant.
Note: The Actions PR will have to be merged before this can be merged, as it references composite actions that are not existent in the current flow but in the one proposed by that PR.
Example workflows (tests commented out for quicker workflow runs, but they are unaffected by these changes):
$ docker run bowtieddevops/stacks-core:4.0.0.0.0 stacks-node version
stacks-node 4.0.0.0.0 (release/4.0.0.0.0:eb8aaf7, release build, linux [x86_64])
INFO [1732236172.154954] [testnet/stacks-node/src/main.rs:283] [main] stacks-node 4.0.0.0.0 (release/4.0.0.0.0:eb8aaf7,
release build, linux [x86_64])
$ docker run bowtieddevops/stacks-core:latest stacks-node version
INFO [1732236216.647136] [testnet/stacks-node/src/main.rs:283] [main] stacks-node 4.0.0.0.0 (release/4.0.0.0.0:eb8aaf7,
release build, linux [x86_64])
stacks-node 4.0.0.0.0 (release/4.0.0.0.0:eb8aaf7, release build, linux [x86_64])
Signer
$ docker run bowtieddevops/stacks-signer:4.0.0.0.0.0 stacks-signer --version
stacks-signer stacks-signer 4.0.0.0.0.0 (release/4.0.0.0.0:eb8aaf7, release build, linux [x86_64])
$ docker run bowtieddevops/stacks-signer:4.0.0.0.0.1 stacks-signer --version
stacks-signer stacks-signer 4.0.0.0.0.1 (release/signer-4.0.0.0.0.1:eb8aaf7, release build, linux [x86_64])
$ docker run bowtieddevops/stacks-signer:4.0.0.0.0.2-rc1 stacks-signer --version
stacks-signer stacks-signer 4.0.0.0.0.2-rc1 (release/signer-4.0.0.0.0.2-rc1:eb8aaf7, release build, linux [x86_64])
$ docker run bowtieddevops/stacks-signer:latest stacks-signer --version
stacks-signer stacks-signer 4.0.0.0.0.1 (release/signer-4.0.0.0.0.1:eb8aaf7, release build, linux [x86_64])
The aim of this PR is to create a signer release every time there is a core release happening, with the tag set as
<core_release>.0
.This PR also moves most of the release workflow out of
stacks-core
and intoactions
repository such that on subsequent changes to the release process, we can easier adjust the workflows without the need of as manystacks-core
pull requests.I've also implemented
latest
docker image tags on non-RC releases and removed thesigner-
word from the signer version tag as it was redundant.Note: The Actions PR will have to be merged before this can be merged, as it references composite actions that are not existent in the current flow but in the one proposed by that PR.
Example workflows (tests commented out for quicker workflow runs, but they are unaffected by these changes):
4.0.0.0.0
andsigner-4.0.0.0.0.0
releases): https://github.com/BowTiedDevOps/stacks-core/actions/runs/11963198211signer-4.0.0.0.0.1
release): https://github.com/BowTiedDevOps/stacks-core/actions/runs/11963781406signer-4.0.0.0.0.2-rc1
release, used to test that docker imagelatest
doesn't update on RC builds): https://github.com/BowTiedDevOps/stacks-core/actions/runs/11963969804Useful Links:
Binaries Version Check:
Node Release
Docker Images Version Check:
Node
Signer