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
Module Federation uses GitHub Actions for automated versioning and publishing:
133
+
Repository maintainers can publish a new version of changed packages to npm.
134
134
135
-
## Release test version
135
+
1. Checkout a new release branch, for example `release-v0.19.0`.
136
+
2. Run `pnpm changeset version` in the package directory to update the version of each package.
137
+
3. Create a pull request, the title should be `release v0.19.1`.
138
+
4. Run the [release action](https://github.com/module-federation/core/actions/workflows/release.yml) to publish packages to npm.
139
+
5. Select `latest` as the release version.
140
+
6. Wait reviewers to approve.
141
+
7. Merge the release pull request to `main`.
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)
136
143
137
-
1. Make sure your branch has added changeset files before releasing the test version
138
-
2. Make sure that both "use workflow from" and "release branch" are split for the test version you want to release
0 commit comments