You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Once the PR is merged, the release workflow will publish the updated packages to npm.
25
+
- At this point, you can begin crafting the release notes for the eventual stable release in the root `CHANGELOG.md` file in the repo
26
+
- Copy the template for a new release and update the version numbers and links accordingly
27
+
- Copy the relevant changelog entries from all packages into the release notes and adjust accordingly
28
+
- Commit these changes directly to the `release-*` branch - they will not trigger a new prerelease since they do not include a changeset
25
29
26
30
### Iterating a pre-release
27
31
@@ -34,6 +38,7 @@ You may need to make changes to a pre-release prior to publishing a final stable
34
38
- Wait for the release workflow to finish and the Changesets action to open its PR that will increment all versions.
35
39
- Review the PR, make any adjustments necessary, and merge it into the `release-*` branch.
36
40
- Once the PR is merged, the release workflow will publish the updated packages to npm.
41
+
- Make sure you copy over the new changeset contents into stable release notes in the root `CHANGELOG.md` file in the repo
37
42
38
43
### Publishing the stable release
39
44
@@ -42,10 +47,11 @@ You may need to make changes to a pre-release prior to publishing a final stable
42
47
- Wait for the release workflow to finish. The Changesets action in the workflow will open a PR that will increment all versions and generate the changelogs for the stable release.
43
48
- Review the updated `CHANGELOG` files and make any adjustments necessary.
0 commit comments