@dialpad/dialtone 9.123.2 → 9.124.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -405,7 +405,7 @@ npm run dev
405
405
 
406
406
  Currently, Dialtone packages are being released in two different ways: `scheduled` and `manually`.
407
407
  The `scheduled` release will only release changes to `production` while `manually` you can choose to release
408
- `alpha`, `beta` or `next` branches.
408
+ `alpha` or `beta` branches.
409
409
 
410
410
  #### Production
411
411
 
@@ -433,11 +433,11 @@ This will trigger the [release action](.github/workflows/release.yml), release c
433
433
  3. Push the `production` branch.
434
434
  4. The [publish action](https://github.com/dialpad/dialtone/actions/workflows/publish.yml) will publish the packages with its corresponding tag.
435
435
 
436
- #### Alpha/Beta/Next
436
+ #### Alpha/Beta
437
437
 
438
438
  1. Merge your changes to the branch you want to release, commit and push to origin. (Note: If your dialtone version number is behind the last production release number, it may fail. Merge in staging or update the version number manually.)
439
439
  2. Go to [GitHub](https://github.com/dialpad/dialtone/actions/workflows/release.yml) and click on `Run workflow`.
440
- 3. Select `alpha`, `beta` or `next` branch.
440
+ 3. Select `alpha` or `beta` branch.
441
441
  4. Select the `package` that you want to release or leave it empty to release all of them.
442
442
 
443
443
  This will trigger the [release action](.github/workflows/release.yml), release changes on the selected branch and automatically publish the selected packages following the next steps: