Commit 67cbbcc
deps: update corepack to 0.14.0
PR-URL: #44509
Reviewed-By: Mohammed Keyvanzadeh <mohammadkeyvanzade94@gmail.com>
Reviewed-By: Darshan Sen <raisinten@gmail.com>
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: Feng Yu <F3n67u@outlook.com>
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>1 parent 9f14dc1 commit 67cbbcc
5 files changed
Lines changed: 108 additions & 66 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -1,5 +1,18 @@ | |||
| 1 | 1 | # Changelog | |
| 2 | 2 | ||
| 3 | + ## [0.14.0](https://github.com/nodejs/corepack/compare/v0.13.0...v0.14.0) (2022-09-02) | ||
| 4 | + | ||
| 5 | + | ||
| 6 | + ### Features | ||
| 7 | + | ||
| 8 | + * add `COREPACK_ENABLE_STRICT` env variable ([#167](https://github.com/nodejs/corepack/issues/167)) ([92b52f6](https://github.com/nodejs/corepack/commit/92b52f6b4918aff968c0942b89fc722ebf57bce2)) | ||
| 9 | + * update package manager versions ([#170](https://github.com/nodejs/corepack/issues/170)) ([6f70bfc](https://github.com/nodejs/corepack/commit/6f70bfc4b6a8a57cccb1ff9cbf2f49240648f1ed)) | ||
| 10 | + | ||
| 11 | + | ||
| 12 | + ### Bug Fixes | ||
| 13 | + | ||
| 14 | + * handle tags including numbers in `prepare` command ([#165](https://github.com/nodejs/corepack/issues/165)) ([5a0727b](https://github.com/nodejs/corepack/commit/5a0727b43976e0dc299151876c0dde2c4a85174d)) | ||
| 15 | + | ||
| 3 | 16 | ## [0.13.0](https://github.com/nodejs/corepack/compare/v0.12.3...v0.13.0) (2022-08-19) | |
| 4 | 17 | ||
| 5 | 18 | ||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -111,12 +111,18 @@ This command will retrieve the given package manager from the specified archive | |||
| 111 | 111 | ||
| 112 | 112 | ## Environment Variables | |
| 113 | 113 | ||
| 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`). | ||
| 115 | - | ||
| 116 | 114 | - `COREPACK_DEFAULT_TO_LATEST` can be set to `0` in order to instruct Corepack | |
| 117 | 115 | not to lookup on the remote registry for the latest version of the selected | |
| 118 | 116 | package manager. | |
| 119 | 117 | ||
| 118 | + - `COREPACK_ENABLE_NETWORK` can be set to `0` to prevent Corepack from accessing | ||
| 119 | + the network (in which case you'll be responsible for hydrating the package | ||
| 120 | + manager versions that will be required for the projects you'll run, using | ||
| 121 | + `corepack hydrate`). | ||
| 122 | + | ||
| 123 | + - `COREPACK_ENABLE_STRICT` can be set to `0` to prevent Corepack from checking | ||
| 124 | + if the package manager corresponds to the one defined for the current project. | ||
| 125 | + | ||
| 120 | 126 | - `COREPACK_HOME` can be set in order to define where Corepack should install | |
| 121 | 127 | the package managers. By default it is set to `%LOCALAPPDATA%\node\corepack` | |
| 122 | 128 | on Windows, and to `$HOME/.cache/node/corepack` everywhere else. | |
0 commit comments