Skip to content

Commit d9b3081

Browse files
bluwybluwy
committed
Merge branch 'main' into pr/kaisermann/1683
2 parents 4507ebd + 8acf5ca commit d9b3081

35 files changed

Lines changed: 1199 additions & 665 deletions

‎.changeset/pink-animals-heal.md‎

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
---
2+
"@changesets/assemble-release-plan": patch
3+
---
4+
5+
fix: Throw a descriptive error if there is an issue with a package name in a changeset

‎.changeset/purple-chefs-film.md‎

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
---
2+
"@changesets/cli": patch
3+
---
4+
5+
Tweaked a hint text printed when one confirms an empty set of packages to be released

‎.changeset/wise-turkeys-behave.md‎

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
---
2+
"@changesets/config": patch
3+
---
4+
5+
Fixed log error link mismatch to remove dot at the end

‎.codesandbox/ci.json‎

Lines changed: 0 additions & 4 deletions
This file was deleted.

‎.github/workflows/ci.yml‎

Lines changed: 3 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -61,14 +61,7 @@ jobs:
6161
runs-on: ubuntu-latest
6262
if: always()
6363
needs: [test, typecheck, lint]
64-
env:
65-
FAILURE: ${{ contains(join(needs.*.result, ','), 'failure') }}
6664
steps:
67-
- name: Check for failure
68-
run: |
69-
echo $FAILURE
70-
if [ "$FAILURE" = "false" ]; then
71-
exit 0
72-
else
73-
exit 1
74-
fi
65+
- name: Exit with error if some jobs are not successful
66+
run: exit 1
67+
if: ${{ always() && (contains(needs.*.result, 'failure') || contains(needs.*.result, 'skipped') || contains(needs.*.result, 'cancelled')) }}

‎docs/adding-a-changeset.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ A changeset is a piece of information about changes made in a branch or commit.
1212

1313
## I am in a multi-package repository (a mono-repo)
1414

15-
1. Run the command line script `yarn changeset` or `npx @changesets/cli`.
15+
1. Run the command line script `yarn changeset` or `pnpm changeset` or `npx @changesets/cli`.
1616
2. Select the packages you want to include in the changeset using <kbd>↑</kbd> and <kbd>↓</kbd> to navigate to packages, and <kbd>space</kbd> to select a package. Hit enter when all desired packages are selected.
1717
3. You will be prompted to select a bump type for each selected package. Select an appropriate bump type for the changes made. See [here](https://semver.org/) for information on semver versioning
1818
4. Your final prompt will be to provide a message to go alongside the changeset. This will be written into the changelog when the next release occurs.
@@ -36,7 +36,7 @@ While not every changeset is going to need a huge amount of detail, a good idea
3636

3737
## I am in a single-package repository
3838

39-
1. Run the command line script `yarn changeset` or `npx @changesets/cli`.
39+
1. Run the command line script `yarn changeset` or `pnpm changeset` or `npx @changesets/cli`.
4040
2. Select an appropriate bump type for the changes made. See [here](https://semver.org/) for information on semver versioning.
4141
3. Your final prompt will be to provide a message to go alongside the changeset. This will be written into the changelog when the next release occurs.
4242

‎docs/config-file-options.md‎

Lines changed: 16 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -211,32 +211,33 @@ Default value: `true`
211211
}
212212
```
213213

214-
---
214+
## `privatePackages` (object or false)
215215

216-
## `privatePackages` (object or `false`)
216+
This option is for setting how private packages should be handled. By default, Changesets will update the changelog for private packages and update their version, but will not create a tag. You can configure this option to change the default behavior.
217217

218-
This option controls whether Changesets should tag and version private packages.
218+
### `version` (optional boolean)
219219

220-
Default value: `{ version: true, tag: false }`
220+
Default value: `true`
221+
222+
When `version` is set to `true`, Changesets will update the version for private packages. If set to `false`, Changesets will not update the version for private packages.
223+
224+
### `tag` (optional boolean)
225+
226+
Default value: `false`
227+
228+
When `tag` is set to `true`, Changesets will create a tag for private packages. If set to `false`, Changesets will not create a tag for private packages.
229+
230+
### Example
221231

222232
```json
223233
{
224234
"privatePackages": {
225-
"tag": true,
226-
"version": true
235+
"version": true,
236+
"tag": false
227237
}
228238
}
229239
```
230240

231-
### Fields:
232-
233-
* `tag` (`boolean`): whether private packages should receive git tags.
234-
* `version` (`boolean`): whether private packages should have their versions bumped.
235-
236-
If set to `false`, private packages will be completely ignored during tagging and versioning.
237-
238-
---
239-
240241
## `changedFilePatterns` (array of strings)
241242

242243
Glob patterns for changed files that should mark a package as changed. Useful to fine-tune what counts as a change (e.g. only source files, ignoring test files, etc).

‎docs/decisions.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ This file is a discussion of some of the rules and design decisions that have go
66

77
Changesets are designed to be as easy to accumulate as possible. As such, when changesets are consumed with `version`, we flatten the version bumps into one single bump at the highest semver range specified.
88

9-
For example: if you run `version`, and we have `packageA` at `1.1.1`, which has two `minor` changesets, and one `patch` changeset, we will bump `packageA` to `1.2.1`.
9+
For example: if you run `version`, and we have `packageA` at `1.1.1`, which has two `minor` changesets, and one `patch` changeset, we will bump `packageA` to `1.2.0`.
1010

1111
This allows changesets to be added and accumulated safely, with the knowledge that packages will only be released once at an appropriate version for the combined set of changesets, while still ensuring each change is captured in the changelog, with an indication of what kind of change it is.
1212

‎docs/intro-to-using-changesets.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ The second two steps can be made part of a CI process.
1717
## Add the changeset tool
1818

1919
```shell
20-
yarn add @changesets/cli && yarn changeset init
20+
yarn add -D @changesets/cli && yarn changeset init
2121
```
2222

2323
or

‎package.json‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@
3636
"dependencies": {
3737
"@babel/cli": "^7.27.0",
3838
"@babel/core": "^7.26.10",
39-
"@babel/preset-env": "^7.26.9",
39+
"@babel/preset-env": "^7.28.5",
4040
"@babel/preset-typescript": "^7.27.0",
4141
"@manypkg/cli": "^0.22.0",
4242
"@preconstruct/cli": "^2.8.12",

0 commit comments

Comments
 (0)