@lerna-lite/publish 4.3.0 → 4.4.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 CHANGED
@@ -592,12 +592,14 @@ lerna will run [npm lifecycle scripts](https://docs.npmjs.com/cli/v8/using-npm/s
592
592
 
593
593
  # `catalog:` protocol
594
594
 
595
- The `catalog:` protocol ([pnpm catalog](https://pnpm.io/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` manually. If you wish them to be bumped automatically, then we strongly suggest that you use the [`workspace:`](#workspace-protocol) protocol instead which is better for local workspace dependencies.
595
+ 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` (or `package.json > workspaces`) manually. If you wish them to be bumped automatically, then we strongly suggest that you use the [`workspace:`](#workspace-protocol) protocol instead of catalog which is better for local workspace dependencies.
596
596
 
597
597
  > [!NOTE]
598
- > Lerna-Lite only has a read access to the catalog and will pull all dependency versions it finds in your `pnpm-workspace.yaml` 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, is that 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).
598
+ > 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).
599
599
 
600
- So for example, if our `pnpm-workspace.yaml` file has the following configuration
600
+ So for example, if our `pnpm-workspace.yaml` (or `package.json > workspaces`) file has the following configuration
601
+
602
+ from a `pnpm-workspace.yaml`
601
603
 
602
604
  ```yaml
603
605
  packages:
@@ -619,7 +621,32 @@ catalogs:
619
621
  react-dom: ^18.2.0
620
622
  ```
621
623
 
622
- and then if one of our package has the following dependencies defined in our `package.json`
624
+ or from project root `package.json > workspaces`
625
+
626
+ ```json
627
+ {
628
+ "name": "my-monorepo",
629
+ "workspaces": {
630
+ "packages": ["packages/*"],
631
+ "catalog": {
632
+ "fs-extra": "^11.2.0",
633
+ "typescript": "^5.7.0"
634
+ },
635
+ "catalogs": {
636
+ "react17": {
637
+ "react": "^17.0.0",
638
+ "react-dom": "^17.0.0"
639
+ },
640
+ "react18": {
641
+ "react": "^18.2.0",
642
+ "react-dom": "^18.2.0"
643
+ }
644
+ }
645
+ }
646
+ }
647
+ ```
648
+
649
+ and then if one of our monorepo package have the following dependencies defined in our `package.json`
623
650
 
624
651
  ```json
625
652
  {
@@ -624,7 +624,7 @@ export class PublishCommand extends Command {
624
624
  }
625
625
  return chain.finally(() => {
626
626
  if (provenanceUrls.size > 0) {
627
- logOutput('The following provenance transparency log entries were created during publishing:');
627
+ logOutput('The following Provenance transparency log entries were created during publishing:');
628
628
  const message = Array.from(provenanceUrls.entries()).map(([pkg, url]) => ` - ${pkg}: ${url}`);
629
629
  logOutput(message.join(EOL));
630
630
  }
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.3.0",
4
+ "version": "4.4.0",
5
5
  "files": [
6
6
  "/dist"
7
7
  ],
@@ -29,18 +29,18 @@
29
29
  "node": "^20.17.0 || >=22.9.0"
30
30
  },
31
31
  "dependencies": {
32
- "@lerna-lite/cli": "4.3.0",
33
- "@lerna-lite/core": "4.3.0",
32
+ "@lerna-lite/cli": "4.4.0",
33
+ "@lerna-lite/core": "4.4.0",
34
34
  "@lerna-lite/npmlog": "4.1.2",
35
- "@lerna-lite/version": "4.3.0",
36
- "@npmcli/arborist": "^9.1.1",
35
+ "@lerna-lite/version": "4.4.0",
36
+ "@npmcli/arborist": "^9.1.2",
37
37
  "@npmcli/package-json": "^6.2.0",
38
38
  "byte-size": "^9.0.1",
39
39
  "columnify": "^1.6.0",
40
40
  "fs-extra": "^11.3.0",
41
41
  "has-unicode": "^2.0.1",
42
42
  "libnpmaccess": "^10.0.1",
43
- "libnpmpublish": "^11.0.0",
43
+ "libnpmpublish": "^11.0.1",
44
44
  "normalize-path": "^3.0.0",
45
45
  "npm-package-arg": "^12.0.2",
46
46
  "npm-packlist": "^10.0.0",
@@ -54,5 +54,5 @@
54
54
  "tinyglobby": "^0.2.14",
55
55
  "tinyrainbow": "^2.0.0"
56
56
  },
57
- "gitHead": "01f6010c1e6ca2c1931efd3c24291f23daeb8e7e"
57
+ "gitHead": "86f9e5487308e6c03906ee54f9daaddf450d69bc"
58
58
  }