Commit d1a9237
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -1,5 +1,20 @@ | |||
| 1 | 1 | # Changelog | |
| 2 | 2 | ||
| 3 | + ## [0.24.0](https://github.com/nodejs/corepack/compare/v0.23.0...v0.24.0) (2023-12-29) | ||
| 4 | + | ||
| 5 | + | ||
| 6 | + ### Features | ||
| 7 | + | ||
| 8 | + * add support for HTTP redirect ([#341](https://github.com/nodejs/corepack/issues/341)) ([6df5063](https://github.com/nodejs/corepack/commit/6df5063b14868ff21499a051e5122fa7211be6ed)) | ||
| 9 | + * add support for rangeless commands ([#338](https://github.com/nodejs/corepack/issues/338)) ([9bee415](https://github.com/nodejs/corepack/commit/9bee4150815113d97f0bd77d62c8d999cfd68ad3)) | ||
| 10 | + * update package manager versions ([#330](https://github.com/nodejs/corepack/issues/330)) ([cfcc280](https://github.com/nodejs/corepack/commit/cfcc28047a788daeef2c0b15ee35a8b1a8149bb6)) | ||
| 11 | + * **yarn:** fallback to npm when `COREPACK_NPM_REGISTRY` is set ([#339](https://github.com/nodejs/corepack/issues/339)) ([0717c6a](https://github.com/nodejs/corepack/commit/0717c6af898e075f57c5694d699a3c51e79a024c)) | ||
| 12 | + | ||
| 13 | + | ||
| 14 | + ### Bug Fixes | ||
| 15 | + | ||
| 16 | + * clarify `EACCES` errors ([#343](https://github.com/nodejs/corepack/issues/343)) ([518bed8](https://github.com/nodejs/corepack/commit/518bed8b7d7c313163c79d31cb9bbc023dba6560)) | ||
| 17 | + | ||
| 3 | 18 | ## [0.23.0](https://github.com/nodejs/corepack/compare/v0.22.0...v0.23.0) (2023-11-05) | |
| 4 | 19 | ||
| 5 | 20 | ||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -177,7 +177,7 @@ This command doesn't change the global version used when running the package | |||
| 177 | 177 | manager from outside the project (use the \`-g,--global\` flag if you wish | |
| 178 | 178 | to do this). | |
| 179 | 179 | ||
| 180 | - ### `corepack install <-g,--global> [--all] [... name@version]` | ||
| 180 | + ### `corepack install <-g,--global> [--all] [... name[@<version>]]` | ||
| 181 | 181 | ||
| 182 | 182 | | Option | Description | | |
| 183 | 183 | | --------------------- | ------------------------------------------ | | |
@@ -189,7 +189,7 @@ Package managers thus installed will be configured as the new default when | |||
| 189 | 189 | calling their respective binaries outside of projects defining the | |
| 190 | 190 | `packageManager` field. | |
| 191 | 191 | ||
| 192 | - ### `corepack pack [--all] [... name@version]` | ||
| 192 | + ### `corepack pack [--all] [... name[@<version>]]` | ||
| 193 | 193 | ||
| 194 | 194 | | Option | Description | | |
| 195 | 195 | | --------------------- | ------------------------------------------ | | |
@@ -200,7 +200,7 @@ calling their respective binaries outside of projects defining the | |||
| 200 | 200 | Download the selected package managers and store them inside a tarball | |
| 201 | 201 | suitable for use with `corepack install -g`. | |
| 202 | 202 | ||
| 203 | - ### `corepack use <name@version>` | ||
| 203 | + ### `corepack use <name[@<version>]>` | ||
| 204 | 204 | ||
| 205 | 205 | When run, this command will retrieve the latest release matching the provided | |
| 206 | 206 | descriptor, assign it to the project's package.json file, and automatically | |
@@ -215,7 +215,7 @@ it. | |||
| 215 | 215 | Unlike `corepack use` this command doesn't take a package manager name nor a | |
| 216 | 216 | version range, as it will always select the latest available version from the | |
| 217 | 217 | same major line. Should you need to upgrade to a new major, use an explicit | |
| 218 | - `corepack use {name}@latest` call. | ||
| 218 | + `corepack use {name}@latest` call (or simply `corepack use {name}`). | ||
| 219 | 219 | ||
| 220 | 220 | ## Environment Variables | |
| 221 | 221 | ||
0 commit comments