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.

Sign up for GitHub

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

Jump to bottom

publishing-libraries docs: Changesets configuration [#9324] #9325

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
+21 −1
Open

publishing-libraries docs: Changesets configuration [#9324] #9325

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
11bf07d
docs(publishing-libraries): publish script requites committing change…
olets Oct 24, 2024
bdbd1c1
docs(publishing-libraries): how to configure changesets for public pa…
olets Oct 24, 2024
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
22 changes: 21 additions & 1 deletion docs/repo-docs/guides/publishing-libraries.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -156,7 +156,17 @@ changeset publish

Linking your publishing flow into Turborepo can make organizing your deploy a lot simpler and faster.

Our recommendation is to add a `publish-packages` script into your root `package.json`:
Our recommendation is to configure Changesets to automatically commit `changeset version`'s changes

```json title="./changeset/config.json"
{
// …
"commit": true,
// …
}
```

and add a `publish-packages` script into your root `package.json`:

```json title="./package.json"
{
Expand All @@ -168,6 +178,16 @@ Our recommendation is to add a `publish-packages` script into your root `package
}
```

If your packages are public, set Changeset's `access` to `public`:

```json title="./changeset/config.json"
{
// …
"access": "public",
// …
}
```

<Callout>
We recommend `publish-packages` so that it doesn't conflict with npm's
built-in `publish` script.
Expand Down