[Docs & CI] Update Release Process Docs and Workflows

[BowTiedDevOps]

Since our release process is split into 2 steps (node - 5 point release, signer - 6 point release), and this is what users are familiar with, we'll have to update the documentation and workflow process to reflect this process:

• Update release-process.md and ci-release.md to reflect the node's 5-point and signer's 6-point release process
• Add a new signer-specific release workflow that doesn't run all the stacks-core tests, but just signer specific ones.

[wileyj]

for the signer specific workflow, i'm thinking we can reduce the amount of steps/tests and possibly even simply the build process. what we have today works, but it can be a bit better/faster.

i do have some unconventional ideas i'll share later on too

[hstove]

One suggestion as part of our release process: it would be great if we manually updated the versions in the various Cargo.toml files. When running cargo build without the ENV variable STACKS_NODE_VERSION, the version string generated (ie in /v2/info and in the signer) defaults to the Cargo.toml version. Thus, when people build from source without the ENV variable, the version shows up as 0.1.0 (in the node).

This is mainly important for the two binaries that people run - stacks-signer/Cargo.toml and testnet/stacks-node/Cargo.toml. But we might as well just do a find-and-replace across all of the packages.

[wileyj]

related to this issue: #5162

[wileyj]

One suggestion as part of our release process: it would be great if we manually updated the versions in the various Cargo.toml files. When running cargo build without the ENV variable STACKS_NODE_VERSION, the version string generated (ie in /v2/info and in the signer) defaults to the Cargo.toml version. Thus, when people build from source without the ENV variable, the version shows up as 0.1.0 (in the node).

This is mainly important for the two binaries that people run - stacks-signer/Cargo.toml and testnet/stacks-node/Cargo.toml. But we might as well just do a find-and-replace across all of the packages.

I like the idea, i'll test this locally to be sure it works as expected for stacks-node as well. for the signer, its not a problem but i'd like to keep the process as similar as possible (meaning we'll want to also update cargo.toml for other workspaces)

[wileyj]

Note to self:

./testnet/stacks-node/Cargo.toml # for stacks-node binary
./libsigner/Cargo.toml # for stacks-signer binary
./stackslib/Cargo.toml # for stacks-inspect

create issue for clarity-cli and blockstack-cli to report version to stdout similar to stacks-node/stacks-signer/stacks-inspect

[hstove]

Ah, I didn't realize this was still opened, but I created #5399 to update the "default" versions. Happy to merge it into this. Unfortunately, it doesn't seem like we can use our version format in Cargo.toml, so I went with a different approach.

[blockstack-devops]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.