History

XGHeaven d27ad76cad Publish canary / Check Changeset exists (push) Waiting to run Details Publish canary / Publish Canary (18) (push) Blocked by required conditions Details CI / build (16.x, ubuntu-latest) (push) Waiting to run Details CI / build (16.x, windows-latest) (push) Waiting to run Details CI / build (18.x, ubuntu-latest) (push) Waiting to run Details CI / build (18.x, windows-latest) (push) Waiting to run Details Version / Version (16) (push) Waiting to run Details fix(miniapp-runtime): enter same page twice then exit should not throw error (#7104 )		2025-06-04 21:11:02 +08:00
..
README.md	feat: release snapshot version (#6229 )	2023-05-11 22:53:45 -07:00
config.json	feat: release snapshot version (#6229 )	2023-05-11 22:53:45 -07:00
little-dodos-impress.md	Feat: add support for custom loaders in rspack configuration (#7078 )	2025-04-14 20:09:44 +08:00
silver-adults-laugh.md	fix: miniapp using absolute path to match route manifest (#7095 )	2025-05-20 17:25:54 +08:00
six-zebras-sniff.md	fix(miniapp-runtime): enter same page twice then exit should not throw error (#7104 )	2025-06-04 21:11:02 +08:00
tame-planets-rush.md	fix: jsxplugs transform (#7076 )	2025-04-10 19:10:19 +08:00

README.md

Changesets

Hello and welcome! This folder has been automatically generated by @changesets/cli, a build tool that works with multi-package repos, or single-package repos to help you version and publish your code. You can find the full documentation for it in our repository

We have a quick list of common questions to get you started engaging with this project in our documentation

Add A Changeset

Read the documentation for more detail.

Publish Snapshot Version

NOTE: It is useful for you to release a version to test your package on your current branch.

Run the following command to publish the snapshot version:

$ npm run release:snapshot

After that, you don't need to commit the change to the branch.

Publish Beta Version

NOTE: Recommend you to publish a beta version on a new branch(such as release-beta) which is checked out from the release* branch.

Run the following command to publish the beta version:

$ npm run release:beta

Then, we need to commit the changes to the branch.

For more detail, please see this documentation.

Publish Latest Version

GitHub bot will automatically create a PR to update the latest versions for the released package.

What we need to do is to merge the PR to the release* branch. After the release* branch was merged to the master branch, the versions will be released automatically.