@lerna-lite/publish 4.7.2 → 4.8.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/README.md +1 -1
- package/package.json +12 -12
package/README.md
CHANGED
|
@@ -596,7 +596,7 @@ lerna will run [npm lifecycle scripts](https://docs.npmjs.com/cli/v8/using-npm/s
|
|
|
596
596
|
|
|
597
597
|
# `catalog:` protocol
|
|
598
598
|
|
|
599
|
-
The `catalog:` protocol ([pnpm catalogs](https://pnpm.io/catalogs), [Bun catalogs](https://bun.sh/docs/install/catalogs)) can be recognized by Lerna-Lite. When publishing, they will be replaced "as is" by reading and using the version range defined in your global catalog. If you need to bump the version of a package in a catalog, you will need to edit `pnpm-workspace.yaml`
|
|
599
|
+
The `catalog:` protocol ([pnpm catalogs](https://pnpm.io/catalogs), [Bun catalogs](https://bun.sh/docs/install/catalogs) or [Yarn catalogs](https://github.com/yarnpkg/berry/tree/master/packages/plugin-catalog)) can be recognized by Lerna-Lite. When publishing, they will be replaced "as is" by reading and using the version range defined in your global catalog(s). If you need to bump the version of a package in a catalog, you will need to edit your root config (e.g `pnpm-workspace.yaml`) manually. If for whatever reasons, you wish them to be bumped automatically, then we strongly suggest that you rather use the [`workspace:`](#workspace-protocol) protocol instead of catalog which is better suited for local workspace dependencies.
|
|
600
600
|
|
|
601
601
|
> [!NOTE]
|
|
602
602
|
> Lerna-Lite only has a read access to the catalog and will pull all dependency versions it finds from your `pnpm-workspace.yaml` (or `package.json`) catalog, but it will **never write** back to that file. If you want version bump while running lerna version/publish commands, then you should use `workspace:` for local dependencies. A side note though, it does work with local dependencies but only if the local dependency version changed in a previous git commit **before** lerna commands are executed (since again Lerna-Lite will never write or update the catalog).
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@lerna-lite/publish",
|
|
3
3
|
"description": "Publish packages in the current workspace",
|
|
4
|
-
"version": "4.
|
|
4
|
+
"version": "4.8.0",
|
|
5
5
|
"files": [
|
|
6
6
|
"/dist"
|
|
7
7
|
],
|
|
@@ -29,15 +29,15 @@
|
|
|
29
29
|
"node": "^20.17.0 || >=22.9.0"
|
|
30
30
|
},
|
|
31
31
|
"dependencies": {
|
|
32
|
-
"@lerna-lite/cli": "4.
|
|
33
|
-
"@lerna-lite/core": "4.
|
|
34
|
-
"@lerna-lite/npmlog": "4.7.
|
|
35
|
-
"@lerna-lite/version": "4.
|
|
36
|
-
"@npmcli/arborist": "^9.1.
|
|
37
|
-
"@npmcli/package-json": "^
|
|
32
|
+
"@lerna-lite/cli": "4.8.0",
|
|
33
|
+
"@lerna-lite/core": "4.8.0",
|
|
34
|
+
"@lerna-lite/npmlog": "4.7.3",
|
|
35
|
+
"@lerna-lite/version": "4.8.0",
|
|
36
|
+
"@npmcli/arborist": "^9.1.4",
|
|
37
|
+
"@npmcli/package-json": "^7.0.1",
|
|
38
38
|
"byte-size": "^9.0.1",
|
|
39
39
|
"columnify": "^1.6.0",
|
|
40
|
-
"fs-extra": "^11.3.
|
|
40
|
+
"fs-extra": "^11.3.2",
|
|
41
41
|
"has-unicode": "^2.0.1",
|
|
42
42
|
"libnpmaccess": "^10.0.1",
|
|
43
43
|
"libnpmpublish": "^11.1.0",
|
|
@@ -47,12 +47,12 @@
|
|
|
47
47
|
"npm-registry-fetch": "^19.0.0",
|
|
48
48
|
"p-map": "^7.0.3",
|
|
49
49
|
"p-pipe": "^4.0.0",
|
|
50
|
-
"pacote": "^21.0.
|
|
50
|
+
"pacote": "^21.0.3",
|
|
51
51
|
"semver": "^7.7.2",
|
|
52
52
|
"ssri": "^12.0.0",
|
|
53
53
|
"tar": "^7.4.3",
|
|
54
|
-
"tinyglobby": "^0.2.
|
|
55
|
-
"tinyrainbow": "^
|
|
54
|
+
"tinyglobby": "^0.2.15",
|
|
55
|
+
"tinyrainbow": "^3.0.3"
|
|
56
56
|
},
|
|
57
|
-
"gitHead": "
|
|
57
|
+
"gitHead": "4184b3d2179e30e474dc522f3052e170927b0fab"
|
|
58
58
|
}
|