chore: update

.changeset/config.json

@@ -5,7 +5,7 @@
   "linked": [],
   "access": "restricted",
   "baseBranch": "main",
-  "fixed": [["@rslib/*"]],
+  "fixed": [["@rslib/*", "rsbuild-plugin-dts"]],
   "___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH": {
     "onlyUpdatePeerDependentsWhenOutOfRange": true,
     "updateInternalDependents": "always"

CONTRIBUTING.md

@@ -117,6 +117,23 @@ pnpm run lint
 
 For VS Code users, you can install the [Biome VS Code extension](https://marketplace.visualstudio.com/items?itemName=biomejs.biome) to see lints while typing.
 
+# Versioning
+
+We use [changesets](https://github.com/changesets/changesets) to manage version. Currently, all rslib packages will use a fixed unified version.
+
+The release notes are automatically generated by [GitHub releases](https://github.com/web-infra-dev/rslib/releases).
+
+## Releasing
+
+Repository maintainers can publish a new version of all packages to npm.
+
+Here are the steps to publish (we generally use CI for releases and avoid publishing npm packages locally):
+
+1. [Create release pull request](https://github.com/web-infra-dev/rslib/actions/workflows/release-pull-request.yml).
+2. [Run the release action](https://github.com/web-infra-dev/rslib/actions/workflows/release.yml).
+3. [Generate the release notes](https://github.com/web-infra-dev/rslib/releases).
+4. Merge the release pull request.
+
 ## Caveats
 
 The project is still in its early stages and under active development, so it possible dependents on Rsbuild or Rspack canary versions to test the latest features. The current canary versions are: