Unified · Split
| @@ -1,6 +1,6 @@ | |||
| 1 | { | 1 | { |
| 2 | "$schema": "https://unpkg.com/@changesets/config@3.1.3/schema.json", | 2 | "$schema": "https://unpkg.com/@changesets/config@3.1.3/schema.json", |
| 3 | "changelog": "@changesets/cli/changelog", | 3 | "changelog": false, |
| 4 | "commit": false, | 4 | "commit": false, |
| 5 | "fixed": [], | 5 | "fixed": [], |
| 6 | "linked": [], | 6 | "linked": [], |
| @@ -45,6 +45,7 @@ That produces: · 44 unmodified lines | |||
| 45 | ## Notes | 45 | ## Notes |
| 46 | 46 | ||
| 47 | - Changesets owns the published CLI version via `apps/cli/package.json`. | 47 | - Changesets owns the published CLI version via `apps/cli/package.json`. |
| 48 | - Changesets changelog file generation is disabled; GitHub release notes are generated at publish time instead. | ||
| 48 | - `scripts/release/sync-versions.mjs` propagates that version across the rest of the repo manifests after `changeset version` runs. | 49 | - `scripts/release/sync-versions.mjs` propagates that version across the rest of the repo manifests after `changeset version` runs. |
| 49 | - The publish workflow supports either npm trusted publishing or an `NPM_TOKEN` secret. | 50 | - The publish workflow supports either npm trusted publishing or an `NPM_TOKEN` secret. |
| 50 | - Re-running the publish workflow for the same tag is safe for packages that are already on npm; existing versions are skipped. | 51 | - Re-running the publish workflow for the same tag is safe for packages that are already on npm; existing versions are skipped. |