Commit 763a63c
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -1,5 +1,14 @@ | |||
| 1 | 1 | # Changelog | |
| 2 | 2 | ||
| 3 | + ## [0.13.0](https://github.com/nodejs/corepack/compare/v0.12.3...v0.13.0) (2022-08-19) | ||
| 4 | + | ||
| 5 | + | ||
| 6 | + ### Features | ||
| 7 | + | ||
| 8 | + * do not use `~/.node` as default value for `COREPACK_HOME` ([#152](https://github.com/nodejs/corepack/issues/152)) ([09e24cf](https://github.com/nodejs/corepack/commit/09e24cf497de27fe92668cf0a8e555f2c7e2530d)) | ||
| 9 | + * download the latest version instead of a pinned one ([#134](https://github.com/nodejs/corepack/issues/134)) ([055b928](https://github.com/nodejs/corepack/commit/055b92807f711b5c8c8be6e62b8d3ce83e1ff002)) | ||
| 10 | + * update package manager versions ([#163](https://github.com/nodejs/corepack/issues/163)) ([af38d5a](https://github.com/nodejs/corepack/commit/af38d5afbbc10d61265b2f4687c5cc498b059b41)) | ||
| 11 | + | ||
| 3 | 12 | ## [0.12.3](https://github.com/nodejs/corepack/compare/v0.12.2...v0.12.3) (2022-08-12) | |
| 4 | 13 | ||
| 5 | 14 | ||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -46,9 +46,16 @@ Just use your package managers as you usually would. Run `yarn install` in Yarn | |||
| 46 | 46 | ||
| 47 | 47 | ## Known Good Releases | |
| 48 | 48 | ||
| 49 | - When running Yarn or pnpm within projects that don't list a supported package manager, Corepack will default to a set of Known Good Releases. In a way, you can compare this to Node.js, where each version ships with a specific version of npm. | ||
| 49 | + When running Corepack within projects that don't list a supported package | ||
| 50 | + manager, it will default to a set of Known Good Releases. In a way, you can | ||
| 51 | + compare this to Node.js, where each version ships with a specific version of npm. | ||
| 50 | 52 | ||
| 51 | - The Known Good Releases can be updated system-wide using the `--activate` flag from the `corepack prepare` and `corepack hydrate` commands. | ||
| 53 | + If there is no Known Good Release for the requested package manager, Corepack | ||
| 54 | + looks up the npm registry for the latest available version and cache it for | ||
| 55 | + future use. | ||
| 56 | + | ||
| 57 | + The Known Good Releases can be updated system-wide using the `--activate` flag | ||
| 58 | + from the `corepack prepare` and `corepack hydrate` commands. | ||
| 52 | 59 | ||
| 53 | 60 | ## Offline Workflow | |
| 54 | 61 | ||
@@ -106,7 +113,13 @@ This command will retrieve the given package manager from the specified archive | |||
| 106 | 113 | ||
| 107 | 114 | - `COREPACK_ENABLE_NETWORK` can be set to `0` to prevent Corepack from accessing the network (in which case you'll be responsible for hydrating the package manager versions that will be required for the projects you'll run, using `corepack hydrate`). | |
| 108 | 115 | ||
| 109 | - - `COREPACK_HOME` can be set in order to define where Corepack should install the package managers. By default it is set to `$HOME/.node/corepack`. | ||
| 116 | + - `COREPACK_DEFAULT_TO_LATEST` can be set to `0` in order to instruct Corepack | ||
| 117 | + not to lookup on the remote registry for the latest version of the selected | ||
| 118 | + package manager. | ||
| 119 | + | ||
| 120 | + - `COREPACK_HOME` can be set in order to define where Corepack should install | ||
| 121 | + the package managers. By default it is set to `%LOCALAPPDATA%\node\corepack` | ||
| 122 | + on Windows, and to `$HOME/.cache/node/corepack` everywhere else. | ||
| 110 | 123 | ||
| 111 | 124 | - `COREPACK_ROOT` has no functional impact on Corepack itself; it's automatically being set in your environment by Corepack when it shells out to the underlying package managers, so that they can feature-detect its presence (useful for commands like `yarn init`). | |
| 112 | 125 | ||
0 commit comments