From 11bf07d6041d6d135aea391d504718cea894742c Mon Sep 17 00:00:00 2001
From: Henry Bley-Vroman <olets@olets.dev>
Date: Wed, 23 Oct 2024 17:41:56 -1000
Subject: [PATCH 1/2] docs(publishing-libraries): publish script requites
 committing changeset version changes [#9324]

---
 docs/repo-docs/guides/publishing-libraries.mdx | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

diff --git a/docs/repo-docs/guides/publishing-libraries.mdx b/docs/repo-docs/guides/publishing-libraries.mdx
index 7e4f631dad0e0..8a0ae25e6c442 100644
--- a/docs/repo-docs/guides/publishing-libraries.mdx
+++ b/docs/repo-docs/guides/publishing-libraries.mdx
@@ -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"
 {

From bdbd1c1bf73641fc1870dbc070f26614a29f3f4b Mon Sep 17 00:00:00 2001
From: Henry Bley-Vroman <olets@olets.dev>
Date: Wed, 23 Oct 2024 17:42:38 -1000
Subject: [PATCH 2/2] docs(publishing-libraries): how to configure changesets
 for public packages

---
 docs/repo-docs/guides/publishing-libraries.mdx | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/docs/repo-docs/guides/publishing-libraries.mdx b/docs/repo-docs/guides/publishing-libraries.mdx
index 8a0ae25e6c442..518c013795ec1 100644
--- a/docs/repo-docs/guides/publishing-libraries.mdx
+++ b/docs/repo-docs/guides/publishing-libraries.mdx
@@ -178,6 +178,16 @@ and add a `publish-packages` script into your root `package.json`:
 }
 ```
 
+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.