@raspberrypifoundation/design-system-react 2.10.4 → 2.11.0

package/README.md

@@ -1,5 +1,8 @@
 # RPF Design System - React
 
+> [!TIP]
+> This package lives in the [design-system monorepo](../../README.md). Read the main README first. It explains how to work within the npm workspace.
+
 The React implementation of the **Raspberry Pi Foundation Design System**
 
 <a href="https://design-system-react.rpf-internal.org/?path=/docs/documentation-introduction--documentation">![React Components](<https://img.shields.io/badge/React-Components_(Storybook)-label?style=for-the-badge&color=hsla(223%2C%209%25%2C%2085%25%2C%201)&labelColor=00AECE>)</a>
@@ -184,28 +187,4 @@ During the migration period you may see a mix of `propTypes` and TypeScript in d
 
 ## Releasing a version
 
-1. Open the [Prep release workflow](https://github.com/RaspberryPiFoundation/design-system-react/actions/workflows/prep-release.yml), select **Run workflow**, and choose a `patch`, `minor`, or `major` version bump.
-2. The workflow creates a branch and opens a draft pull request that:
-   - bumps the version in `package.json`; and
-   - changes the `Unreleased` heading in `CHANGELOG.md` to the new version and release date.
-3. Review the generated changes, mark the pull request ready for review, and merge it into `main`.
-4. Create a matching tag. The tag must start with `v`, for example `v2.10.4`. You can do this in either of these ways:
-
-- **Using the command line:** pull the merged commit, then create and push the tag:
-
-  ```sh
-  git checkout main
-  git pull
-  git tag v2.10.4
-  git push origin v2.10.4
-  ```
-
-- **Using the GitHub UI:**
-  1. Open the [new release page](https://github.com/RaspberryPiFoundation/design-system-react/releases/new).
-  2. Select **Choose a tag** and enter the new version, including the `v` prefix.
-  3. Select **Create new tag on publish**.
-  4. Confirm that the tag will target the `main` branch.
-
-5. On the [new release page](https://github.com/RaspberryPiFoundation/design-system-react/releases/new), select the matching tag, generate the default release notes, and publish the release. If you chose to create the tag through the GitHub UI, publishing the release creates the tag at the same time.
-
-Publishing the GitHub release triggers GitHub Actions to build the package and publish it to npm using npm Trusted Publishing. Releases do not require an `NPM_TOKEN` or `NODE_AUTH_TOKEN` repository secret.
+This monorepo uses release-please to publish releases. See [Releases (release-please)](../../README.md#releases-release-please) in the main README.