Configure semantic-release #38
Conversation
ericcrosson-bitgo
changed the title
|
I have added one git tag per package to BitGo/api-ts, which should set the initial version that semantic-release uses to calculate the next version numbers: https://github.com/BitGo/api-ts/tags Here is the documentation on how semantic-release uses existing git tags, note that I've dropped the leading |
ericcrosson-bitgo
force-pushed
the
configure-semantic-release
branch
from
58e50a5 to
6039ef3
Compare
as recommended by the multi-semantic-release package[^1]. [^1]: https://github.com/dhoulb/multi-semantic-release#overview
ericcrosson-bitgo
force-pushed
the
configure-semantic-release
branch
from
6039ef3 to
d95cdfc
Compare
including GitHub workflows
> Using the `fix` conventional-commits scope instead of `ci` as a > straightforward way to force a release This commit configures semantic-release to publish new versions when semantically appropriate to npm and create a corresponding GitHub Release. This punts management of a changelog to BitGo#37. Closes BitGo#36.
ericcrosson-bitgo
force-pushed
the
configure-semantic-release
branch
from
d95cdfc to
0048003
Compare
|
🎉 This PR is included in version 1.0.0-beta.1 🎉 The release is available on npm package (@beta dist-tag) Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 0.2.0-beta.1 🎉 The release is available on npm package (@beta dist-tag) Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 0.1.1-beta.1 🎉 The release is available on npm package (@beta dist-tag) Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 0.2.0-beta.1 🎉 The release is available on npm package (@beta dist-tag) Your semantic-release bot 📦🚀 |
2 participants
ci: configure semantic-release
This commit configures semantic-release to publish new versions
when semantically appropriate to npm and create a corresponding
GitHub Release.
This punts management of a changelog to #37.
Closes #36.