Ci/add release plz

[notmandatory]

Description

Add a GitHub Actions workflow that uses release-plz to automate creating release PRs, publishing to crates.io, tagging, and creating GitHub releases via OIDC trusted publishing and environment-gated approvals. Update DEVELOPMENT_CYCLE.md with the new release process.

Removed changelog section from pr template since the release_plz workflow will use conventional commit messages to update the CHANGELOG. Also removed the API breaking checkbox since it doesn't apply to binary apps like bdk-cli.

Notes to the reviewers

Before this workflow will work I'll need to update the repo and crates.io settings for the release-plz action.

1. Change GitHub Actions permissions on GitHub repo settings; change "Workflow permissions" to allow GitHub Actions to create and approve pull requests.
2. Add "Trusted Publishing" on crates.io for the crate with workflow name "release-plz.yml", environment "release". Require trusted publishing for all new versions.
3. Add "release" environment on GitHub repo settings to specify "required reviewers" who can approve a release. Should be at least two people.

You can see how this workflow works here: https://github.com/bitcoindevkit/rust-cktap/actions/workflows/release-plz.yml

Also bumped GitHub Actions version:

• actions/checkout@v6 to v7
• setup-rust-toolchain@v1 to v2
• codecov/codecov-action@v5 to v7

Checklists

All Submissions:

• I've signed all my commits
• I followed the contribution guidelines
• I ran cargo fmt and cargo clippy before committing

[tvpeter]

Since the release templates will no longer be used, do we update them to contain the steps in triggering the workflow or we will delete them?

[notmandatory]

Good point, I've removed the minor_release.md template since we don't need it. We should still create a summary for posting about releases on social media, but that can be done ad-hoc for now. I've found trying to use one summary everywhere didn't really work anyway.

[tvpeter]

Thank you for working on this release tool.

Aside the nits, I am wondering if the Release Tags will still be signed with this tool (since there is no way of testing it locally). If the tags will no longer be signed, is there a way that users can verify a Release?

I tested some parts locally and it worked well, though the format for the Changelog entries are a bit different. They are based on commit messages. So we will have to ensure commit messages are properly curated.

Thank you.

[notmandatory]

Aside the nits, I am wondering if the Release Tags will still be signed with this tool (since there is no way of testing it locally). If the tags will no longer be signed, is there a way that users can verify a Release?

The new tags are signed but by the "bitcoindevkit-release-plz" bot. You can see an example here:

https://github.com/bitcoindevkit/rust-cktap/releases/tag/rust-cktap-v0.3.0

This at least means that only someone authorized to publish releases via the bot, enforced by GitHub settings, created the release tag.

I tested some parts locally and it worked well, though the format for the Changelog entries are a bit different. They are based on commit messages. So we will have to ensure commit messages are properly curated.

During PR reviews we'll need to make sure commits follow the conventional commits style. But if there are problems with the release-plz auto generated CHANGELOG, the PR can still be manually edited to fix mistakes before it's merged (release-plz won't overwrite manual changes).

[notmandatory]

The new tags are signed but by the "bitcoindevkit-release-plz" bot. You can see an example here:

https://github.com/bitcoindevkit/rust-cktap/releases/tag/rust-cktap-v0.3.0

Sorry I take it back, the tags show as verified by GitHub, but they don't have a proper signature in the git history:

$ git tag -v rust-cktap-v0.3.0
object 090abe33212aa1f9582d7ef22faa2e2634f0316f
type commit
tag rust-cktap-v0.3.0
tagger bitcoindevkit-release-plz[bot] <327630426+bitcoindevkit-release-plz[bot]@users.noreply.github.com> 1789143429 +0000

chore: Release package rust-cktap version 0.3.0error: no signature found

[tvpeter]

The new tags are signed but by the "bitcoindevkit-release-plz" bot. You can see an example here:
https://github.com/bitcoindevkit/rust-cktap/releases/tag/rust-cktap-v0.3.0

Sorry I take it back, the tags show as verified by GitHub, but they don't have a proper signature in the git history:

$ git tag -v rust-cktap-v0.3.0
object 090abe33212aa1f9582d7ef22faa2e2634f0316f
type commit
tag rust-cktap-v0.3.0
tagger bitcoindevkit-release-plz[bot] <327630426+bitcoindevkit-release-plz[bot]@users.noreply.github.com> 1789143429 +0000

chore: Release package rust-cktap version 0.3.0error: no signature found

I think it is non-blocking and the tagger label should suffice for now.

[tvpeter]

tACK 769a7a2

[notmandatory]

I force-pushed a rebase on the latest master for a cleaner merge.