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
Repository maintainers can publish a new version of changed packages to npm.
133
134
134
135
1. Checkout a new release branch, for example `release-v0.19.0`.
135
136
2. Run `pnpm changeset version` in the package directory to update the version of each package.
136
-
3. Create a pull request, the title should be `relea se v0.19.1`.
137
+
3. Create a pull request, the title should be `release v0.19.1`.
137
138
4. Run the [release action](https://github.com/module-federation/core/actions/workflows/release.yml) to publish packages to npm.
138
139
5. Wait reviewers to approve.
139
140
6. Merge the release pull request to `main`.
140
141
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)
141
142
142
-
## Release test version
143
+
## Release preview version
144
+
145
+
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.
143
147
144
-
1. Run the [preview action](https://github.com/module-federation/core/actions/workflows/preview.yml) to publish preview packages via [pkg-pr-new](https://github.com/stackblitz-labs/pkg.pr.new).
0 commit comments