zcash_script 0.6.0

zcash_script

Rust implementation of the Zcash Script language..

Publishing New Releases

This crate maintains two concurrent release lines: a main-based release (0.5.x) and a backport release on a separate branch (0.4.x). Both must be released together when publishing fixes that apply to both lines.

Main-line release (0.5.x)

1. Decide the release level (patch, minor, or major).
2. Bump the version and apply changelog/doc replacements:

   cargo release version --verbose --execute --allow-branch '*' -p zcash_script patch # [ major | minor ]
   cargo release replace --verbose --execute --allow-branch '*' -p zcash_script
   

3. Update CHANGELOG.md.
4. Open a PR with the changes, get it reviewed, and wait for CI to pass.
5. Create a new GitHub release for the tag.
6. Publish the crate:

   cargo release publish --verbose --execute -p zcash_script
   

Backport release (0.4.x)

1. Create a base branch from the previous release tag (e.g. zcash_script-v0.4.2):

   git checkout -b backport/zcash_script-0.4.3-base zcash_script-v0.4.2
   git push origin backport/zcash_script-0.4.3-base
   

2. Create a working branch from the base branch:

   git checkout -b backport/zcash_script-0.4.3
   

3. Cherry-pick the relevant commits from main (excluding release/merge commits).
4. Bump the version and apply replacements on the backport branch:

   cargo release version --verbose --execute --allow-branch '*' -p zcash_script patch
   cargo release replace --verbose --execute --allow-branch '*' -p zcash_script
   

5. Update CHANGELOG.md.
6. Open a PR from backport/zcash_script-0.4.3 targeting backport/zcash_script-0.4.3-base, get it reviewed, and wait for CI to pass.
7. Create a new GitHub release for the tag.
8. Publish the crate from the backport tag:

   cargo release publish --verbose --execute -p zcash_script