mirror/pnpm
1
0
Fork 0
mirror of https://github.com/pnpm/pnpm.git synced 2026-07-17 19:22:20 -04:00
Code Issues Packages Projects Releases Wiki Activity

chore(release): 10.33.3

Browse Source
This commit is contained in:
Zoltan Kochan
2026-05-04 23:07:56 +02:00
parent 3349432a0f
commit d4f0fffaaf
13 changed files with 23 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
.changeset/v10-self-update-darwin-x64-to-pnpm-js.md
View File

@@ -1,6 +0,0 @@
---
"@pnpm/tools.plugin-commands-self-updater": patch
"pnpm": patch
---
When self-updating from v10's `@pnpm/exe` to v11+ on Intel macOS (darwin-x64), `pnpm self-update` now transparently switches to the JS-only `pnpm` package on npm instead of installing `@pnpm/exe@v11+` (which doesn't ship a working binary for Intel Macs because of an upstream Node.js SEA bug — see [#11423](https://github.com/pnpm/pnpm/issues/11423) and [nodejs/node#62893](https://github.com/nodejs/node/issues/62893)). Without this, the self-update would silently leave the user with no working `pnpm` binary. The new install requires Node.js to be available on `PATH`; a warning is printed when the swap happens. All other host/version combinations are unchanged.

6
.changeset/v10-self-update-no-downgrade.md
View File

@@ -1,6 +0,0 @@
---
"@pnpm/tools.plugin-commands-self-updater": patch
"pnpm": patch
---
`pnpm self-update` (with no version argument) no longer downgrades pnpm when the registry's `latest` dist-tag points to an older release than the currently active version. Run `pnpm self-update latest` to force a downgrade [#11418](https://github.com/pnpm/pnpm/issues/11418).

7
pnpm/CHANGELOG.md
View File

@@ -1,5 +1,12 @@
# pnpm
## 10.33.3
### Patch Changes
- When self-updating from v10's `@pnpm/exe` to v11+ on Intel macOS (darwin-x64), `pnpm self-update` now transparently switches to the JS-only `pnpm` package on npm instead of installing `@pnpm/exe@v11+` (which doesn't ship a working binary for Intel Macs because of an upstream Node.js SEA bug — see [#11423](https://github.com/pnpm/pnpm/issues/11423) and [nodejs/node#62893](https://github.com/nodejs/node/issues/62893)). Without this, the self-update would silently leave the user with no working `pnpm` binary. The new install requires Node.js to be available on `PATH`; a warning is printed when the swap happens. All other host/version combinations are unchanged.
- `pnpm self-update` (with no version argument) no longer downgrades pnpm when the registry's `latest` dist-tag points to an older release than the currently active version. Run `pnpm self-update latest` to force a downgrade [#11418](https://github.com/pnpm/pnpm/issues/11418).
## 10.33.2
### Patch Changes

2
pnpm/artifacts/exe/package.json
View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/exe",
"version": "10.33.2",
"version": "10.33.3",
"description": "Fast, disk space efficient package manager",
"keywords": [
"pnpm",

2
pnpm/artifacts/linux-arm64/package.json
View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/linux-arm64",
"version": "10.33.2",
"version": "10.33.3",
"keywords": [
"pnpm",
"pnpm10",

2
pnpm/artifacts/linux-x64/package.json
View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/linux-x64",
"version": "10.33.2",
"version": "10.33.3",
"keywords": [
"pnpm",
"pnpm10",

2
pnpm/artifacts/macos-arm64/package.json
View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/macos-arm64",
"version": "10.33.2",
"version": "10.33.3",
"keywords": [
"pnpm",
"pnpm10",

2
pnpm/artifacts/macos-x64/package.json
View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/macos-x64",
"version": "10.33.2",
"version": "10.33.3",
"keywords": [
"pnpm",
"pnpm10",

2
pnpm/artifacts/win-arm64/package.json
View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/win-arm64",
"version": "10.33.2",
"version": "10.33.3",
"keywords": [
"pnpm",
"pnpm10",

2
pnpm/artifacts/win-x64/package.json
View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/win-x64",
"version": "10.33.2",
"version": "10.33.3",
"keywords": [
"pnpm",
"pnpm10",

2
pnpm/package.json
View File

@@ -1,6 +1,6 @@
{
"name": "pnpm",
"version": "10.33.2",
"version": "10.33.3",
"description": "Fast, disk space efficient package manager",
"keywords": [
"pnpm",

7
tools/plugin-commands-self-updater/CHANGELOG.md
View File

@@ -1,5 +1,12 @@
# @pnpm/tools.plugin-commands-self-updater
## 1000.1.56
### Patch Changes
- c54bcfd: When self-updating from v10's `@pnpm/exe` to v11+ on Intel macOS (darwin-x64), `pnpm self-update` now transparently switches to the JS-only `pnpm` package on npm instead of installing `@pnpm/exe@v11+` (which doesn't ship a working binary for Intel Macs because of an upstream Node.js SEA bug — see [#11423](https://github.com/pnpm/pnpm/issues/11423) and [nodejs/node#62893](https://github.com/nodejs/node/issues/62893)). Without this, the self-update would silently leave the user with no working `pnpm` binary. The new install requires Node.js to be available on `PATH`; a warning is printed when the swap happens. All other host/version combinations are unchanged.
- 3349432: `pnpm self-update` (with no version argument) no longer downgrades pnpm when the registry's `latest` dist-tag points to an older release than the currently active version. Run `pnpm self-update latest` to force a downgrade [#11418](https://github.com/pnpm/pnpm/issues/11418).
## 1000.1.55
### Patch Changes

2
tools/plugin-commands-self-updater/package.json
View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/tools.plugin-commands-self-updater",
"version": "1000.1.55",
"version": "1000.1.56",
"description": "A command for updating pnpm itself",
"keywords": [
"pnpm",