In order to keep master clean for bugfixes during the transition period, we should release from the Protocol 22 branch which has a well-defined set of already-approved and merged PRs (see lucky https://github.com/stellar/js-stellar-base/pull/777).
This PR tags off the version, publishes under the beta tag on NPM, and updates the changelog.
Note that this is tagged as a beta instead of an rc so that we can properly handle any anticipated changes to core that occur throughout the release process (e.g. patch fixes after v22.0.0 that require XDR structure or behavior changes), as was the case with Protocol 20.
In order to keep
master
clean for bugfixes during the transition period, we should release from the Protocol 22 branch which has a well-defined set of already-approved and merged PRs (see lucky https://github.com/stellar/js-stellar-base/pull/777).This PR tags off the version, publishes under the
beta
tag on NPM, and updates the changelog.Note that this is tagged as a
beta
instead of anrc
so that we can properly handle any anticipated changes to core that occur throughout the release process (e.g. patch fixes afterv22.0.0
that require XDR structure or behavior changes), as was the case with Protocol 20.