ci: alpha/beta releases #120
Conversation
## [1.23.6-alpha.1](dialtone-tokens/v1.23.5...dialtone-tokens/v1.23.6-alpha.1) (2024-01-22) ### Bug Fixes * remove release command from tokens ([ef84641](ef84641))
# [2.112.0-alpha.2](dialtone-vue2/v2.112.0-alpha.1...dialtone-vue2/v2.112.0-alpha.2) (2024-01-22) ### Bug Fixes * test alpha release ([4c9f966](4c9f966))
juliodialpad
requested review from
iropolo,
francisrupert,
braddialpad and
ninamarina
as code owners
# Conflicts: # CHANGELOG.json # CHANGELOG.md # package.json # packages/dialtone-vue2/CHANGELOG.json # packages/dialtone-vue2/CHANGELOG.md # packages/dialtone-vue2/package.json
juliodialpad
added
the
no-visual-test
|
✔️ Deploy previews ready! |
|
I have a question related to this, although not particularly with the code: which are our alpha / beta users? how much time does a feature stay in alpha / beta before going to production? |
We don't really have a specific workflow of putting something into alpha/beta and then promoting to staging, we mostly use alpha/beta when we need to test something on product before making the actual release. |
|
Yes it can be used for any situation where we need to do a "side release" for some reason. Testing stuff on product is one usage. Another one is fixing bugs in Dialpad beta. If there is a Dialtone related bug in beta that needs to be fixed before release we might not want to just push the latest dialtone update to beta that has 8 other updates in it because that could potentially break something else. In this case we could make a release on the alpha or beta branch that is the same version dialpad beta is using with just the bug fix added to it. |
README.md
Outdated
| @@ -113,11 +113,27 @@ pnpm nx build dialtone-documentation | |||
|
|
|||
| ### Releasing | |||
|
|
|||
| Running this commands will automatically release all packages that need to be released. | |||
There was a problem hiding this comment.
"this command" or "these commands"
README.md
Outdated
|
|
||
| #### Production | ||
|
|
||
| Note: needs to be run while on staging branch. |
There was a problem hiding this comment.
Slightly more detail about what this command actually does.
Merges staging to production branch
publishes the library package to npm
deploys the documentation site.
README.md
Outdated
|
|
||
| #### Alpha/Beta | ||
|
|
||
| Note: needs to be run while on your feature branch. |
| @@ -1,3 +1,10 @@ | |||
| ## [1.23.6-alpha.1](https://github.com/dialpad/dialtone/compare/dialtone-tokens/v1.23.5...dialtone-tokens/v1.23.6-alpha.1) (2024-01-22) | |||
There was a problem hiding this comment.
hmm should alpha releases actually show up in this changelog?
There was a problem hiding this comment.
We were showing them before on dialtone-vue and legacy dialtone. I remember having issues with them but I think they were because we weren't merging changes back.
I'll check if there's a way to only put "production" changes on the changelog.
| @@ -1,6 +1,6 @@ | |||
| { | |||
| "name": "@dialpad/dialtone-tokens", | |||
| "version": "1.23.5", | |||
| "version": "1.23.6-alpha.1", | |||
There was a problem hiding this comment.
I think we don't want to merge this version to staging right?
There was a problem hiding this comment.
Right, I'll revert that changes.
I don't think we'll have issues with versions as the tags will be kept.
|
✔️ Deploy previews ready! |
|
✔️ Deploy previews ready! |
|
✔️ Deploy previews ready! |
CI: Alpha / Beta releases
Obligatory GIF (super important!)
🛠️ Type Of Change
These types will increment the version number on release:
These types will not increment the version number, but will still deploy to documentation site on release:
📖 Jira Ticket
https://dialpad.atlassian.net/browse/DLT-1484
📖 Description
release.shscript to support releasing alpha and beta.💡 Context
After migrating to monorepo we were missing the ability to release alpha/beta versions.
📝 Checklist
For all PRs:
🔮 Next Steps