Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve "Releasing new versions" section formatting #2954

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,11 +29,11 @@ VITE_PROJECT_ID="your_project_id"
4. Run gallery, laboratory or examples in a separate tab i.e. `pnpm laboratory`

# Releasing new versions
> [!NOTE]
anonployed marked this conversation as resolved.
Show resolved Hide resolved
> If you need to release a canary/alpha/beta, you need to enter prelease mode first.

### Enter prelease mode [Optional]

If you need to release a canary/alpha/beta you need to enter prelease mode first

```sh
pnpm changeset:pre <release tag>
```
Expand All @@ -42,7 +42,6 @@ For example: `pnpm changeset:pre a123bas2`

### Generate changeset

If you need to release a canary/alpha/beta you need to enter prelease mode first

```sh
pnpm changeset
Expand Down