@pnpm/releasing.exportable-manifest 1100.1.15 → 1100.2.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +13 -0
- package/lib/overridePublishConfig.js +5 -0
- package/package.json +8 -8
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,18 @@
|
|
|
1
1
|
# @pnpm/exportable-manifest
|
|
2
2
|
|
|
3
|
+
## 1100.2.0
|
|
4
|
+
|
|
5
|
+
### Minor Changes
|
|
6
|
+
|
|
7
|
+
- Added support for `publishConfig.name`, which publishes a package under a different name than the one its manifest carries in the workspace. It is for a project whose published name is already taken by a sibling project, which otherwise has to be renamed by a build step just before publishing. Only the published artifact is renamed — dependents, `pnpm-lock.yaml`, and release tooling keep addressing the project by its manifest name — and the new name reaches the packed manifest, the tarball filename, and everything that addresses the package at the registry: the already-published check of `pnpm publish -r`, its registry selection, and the release-planning probes of `pnpm change status` and `pnpm version -r` [#13345](https://github.com/pnpm/pnpm/issues/13345).
|
|
8
|
+
|
|
9
|
+
### Patch Changes
|
|
10
|
+
|
|
11
|
+
- Updated dependencies:
|
|
12
|
+
- @pnpm/bins.resolver@1100.0.12
|
|
13
|
+
- @pnpm/types@1101.7.0
|
|
14
|
+
- @pnpm/workspace.project-manifest-reader@1100.0.21
|
|
15
|
+
|
|
3
16
|
## 1100.1.15
|
|
4
17
|
|
|
5
18
|
### Patch Changes
|
|
@@ -1,6 +1,11 @@
|
|
|
1
1
|
import { isEmpty } from 'ramda';
|
|
2
2
|
// property keys that are copied from publishConfig into the manifest
|
|
3
3
|
const PUBLISH_CONFIG_WHITELIST = new Set([
|
|
4
|
+
// Lets a package be published under a name it cannot carry in the workspace
|
|
5
|
+
// — typically because a sibling project already owns that name. Nothing else
|
|
6
|
+
// in the workspace observes the rename: dependents, pnpm-lock.yaml, and the
|
|
7
|
+
// changeset ledger all keep addressing the project by its manifest name.
|
|
8
|
+
'name',
|
|
4
9
|
// manifest fields that may make sense to overwrite
|
|
5
10
|
'bin',
|
|
6
11
|
'engines',
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@pnpm/releasing.exportable-manifest",
|
|
3
|
-
"version": "1100.
|
|
3
|
+
"version": "1100.2.0",
|
|
4
4
|
"description": "Creates an exportable manifest",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"pnpm",
|
|
@@ -28,12 +28,12 @@
|
|
|
28
28
|
],
|
|
29
29
|
"dependencies": {
|
|
30
30
|
"@npm/types": "^2.1.0",
|
|
31
|
-
"@pnpm/bins.resolver": "1100.0.
|
|
31
|
+
"@pnpm/bins.resolver": "1100.0.12",
|
|
32
32
|
"@pnpm/catalogs.resolver": "1100.0.1",
|
|
33
33
|
"@pnpm/error": "1100.1.0",
|
|
34
34
|
"@pnpm/resolving.jsr-specifier-parser": "1100.0.3",
|
|
35
|
-
"@pnpm/types": "1101.
|
|
36
|
-
"@pnpm/workspace.project-manifest-reader": "1100.0.
|
|
35
|
+
"@pnpm/types": "1101.7.0",
|
|
36
|
+
"@pnpm/workspace.project-manifest-reader": "1100.0.21",
|
|
37
37
|
"p-map-values": "^0.1.0",
|
|
38
38
|
"ramda": "npm:@pnpm/ramda@0.28.1"
|
|
39
39
|
},
|
|
@@ -41,11 +41,11 @@
|
|
|
41
41
|
"@jest/globals": "30.4.1",
|
|
42
42
|
"@pnpm/catalogs.config": "1100.0.3",
|
|
43
43
|
"@pnpm/catalogs.types": "1100.0.1",
|
|
44
|
-
"@pnpm/hooks.pnpmfile": "1100.0.
|
|
45
|
-
"@pnpm/prepare": "1100.0.
|
|
46
|
-
"@pnpm/releasing.exportable-manifest": "1100.
|
|
44
|
+
"@pnpm/hooks.pnpmfile": "1100.0.23",
|
|
45
|
+
"@pnpm/prepare": "1100.0.23",
|
|
46
|
+
"@pnpm/releasing.exportable-manifest": "1100.2.0",
|
|
47
47
|
"@types/cross-spawn": "^6.0.6",
|
|
48
|
-
"@types/ramda": "0.
|
|
48
|
+
"@types/ramda": "0.32.0",
|
|
49
49
|
"cross-spawn": "^7.0.6",
|
|
50
50
|
"write-yaml-file": "^6.0.0"
|
|
51
51
|
},
|