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
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -136,15 +136,17 @@ Repository maintainers can publish a new version of changed packages to npm.
136
136
2. Run `pnpm changeset version` in the package directory to update the version of each package.
137
137
3. Create a pull request, the title should be `release v0.19.1`.
138
138
4. Run the [release action](https://github.com/module-federation/core/actions/workflows/release.yml) to publish packages to npm.
139
-
5. Wait reviewers to approve.
140
-
6. Merge the release pull request to `main`.
139
+
5. Select `latest` as the release version.
140
+
6. Wait reviewers to approve.
141
+
7. Merge the release pull request to `main`.
141
142
7. Generate the [release notes](https://github.com/module-federation/core/releases) via GitHub, see [Automatically generated release notes](https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes)
142
143
143
144
## Release preview version
144
145
145
146
1. Make sure your branch has added changeset files before releasing the preview version.
146
-
2. Run the [preview action](https://github.com/module-federation/core/actions/workflows/preview.yml) to publish preview packages.
147
-
147
+
2. Run the [release action](https://github.com/module-federation/core/actions/workflows/release.yml) to publish packages to npm.
0 commit comments