@lerna-lite/publish 3.12.0 → 3.12.1

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.
Files changed (2) hide show
  1. package/README.md +7 -6
  2. package/package.json +8 -8
package/README.md CHANGED
@@ -579,7 +579,7 @@ lerna will run [npm lifecycle scripts](https://docs.npmjs.com/cli/v8/using-npm/s
579
579
 
580
580
  # `catalog:` protocol
581
581
 
582
- The `catalog:` protocol ([pnpm catalog](https://pnpm.io/catalogs)) can be recognized by Lerna-Lite. When publishing, they will be replaced as is and use 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 suggest using [`workspace:`](#workspace-protocol) protocol instead for any workspace dependencies.
582
+ 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.
583
583
 
584
584
  So for example, if our `pnpm-workspace.yaml` file has the following configuration
585
585
 
@@ -594,17 +594,16 @@ catalog:
594
594
 
595
595
  # named catalogs are also supported
596
596
  catalogs:
597
- # Can be referenced through "catalog:react17"
597
+ # Can be referenced through "catalog:react17" or "catalog:react18"
598
598
  react17:
599
599
  react: ^17.0.0
600
600
  react-dom: ^17.0.0
601
- # Can be referenced through "catalog:react18"
602
601
  react18:
603
602
  react: ^18.2.0
604
603
  react-dom: ^18.2.0
605
604
  ```
606
605
 
607
- and then one of our package with the following dependencies defined in our `package.json`
606
+ and then if one of our package has the following dependencies defined in our `package.json`
608
607
 
609
608
  ```json
610
609
  {
@@ -623,7 +622,7 @@ and then one of our package with the following dependencies defined in our `pack
623
622
 
624
623
  #### versions that will be published
625
624
 
626
- Lerna-Lite will replace all `catalog:` protocol with the version ranges defined in the global catalog(s) and publish the following:
625
+ Lerna-Lite will resolve all `catalog:` protocol by extracting the version ranges defined in the global catalog(s) and will publish the following:
627
626
 
628
627
  ```json
629
628
  {
@@ -642,7 +641,7 @@ Lerna-Lite will replace all `catalog:` protocol with the version ranges defined
642
641
 
643
642
  # `workspace:` protocol
644
643
 
645
- The `workspace:` protocol ([pnpm workspace](https://pnpm.io/workspaces), [yarn workspace](https://yarnpkg.com/features/workspaces#workspace-ranges-workspace)) is also supported by Lerna-Lite. We also strongly suggest that you use this in combo with the new [`--sync-workspace-lock`](https://github.com/lerna-lite/lerna-lite/tree/main/packages/version#--sync-workspace-lock) flag to properly update your root project lock file. When publishing, it will replace any `workspace:` dependencies by:
644
+ The `workspace:` protocol ([pnpm workspace](https://pnpm.io/workspaces), [yarn workspace](https://yarnpkg.com/features/workspaces#workspace-ranges-workspace)) is also supported by Lerna-Lite. You could also use this in combo with the new [`--sync-workspace-lock`](https://github.com/lerna-lite/lerna-lite/tree/main/packages/version#--sync-workspace-lock) flag to properly update your root project lock file. When publishing, it will replace any `workspace:` dependencies by:
646
645
 
647
646
  - the corresponding version in the target workspace (if you use `workspace:*`, `workspace:~`, or `workspace:^`)
648
647
  - the associated semver range (for any other range type)
@@ -677,6 +676,8 @@ The library is doing a strict match and it will transform and publish the follow
677
676
  }
678
677
  ```
679
678
 
679
+ > **Note** semver range with an operator (ie `workspace:>=2.0.0`) are also supported but will never be mutated.
680
+
680
681
  ## FAQ
681
682
 
682
683
  ### Recovering from a network error
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": "3.12.0",
4
+ "version": "3.12.1",
5
5
  "files": [
6
6
  "/dist"
7
7
  ],
@@ -29,10 +29,10 @@
29
29
  "node": "^18.0.0 || >=20.0.0"
30
30
  },
31
31
  "dependencies": {
32
- "@lerna-lite/cli": "3.12.0",
33
- "@lerna-lite/core": "3.12.0",
34
- "@lerna-lite/npmlog": "3.12.0",
35
- "@lerna-lite/version": "3.12.0",
32
+ "@lerna-lite/cli": "3.12.1",
33
+ "@lerna-lite/core": "3.12.1",
34
+ "@lerna-lite/npmlog": "3.12.1",
35
+ "@lerna-lite/version": "3.12.1",
36
36
  "@npmcli/arborist": "^7.5.4",
37
37
  "@npmcli/package-json": "^5.2.1",
38
38
  "byte-size": "^9.0.1",
@@ -48,12 +48,12 @@
48
48
  "p-map": "^7.0.3",
49
49
  "p-pipe": "^4.0.0",
50
50
  "pacote": "^18.0.6",
51
- "semver": "^7.7.0",
51
+ "semver": "^7.7.1",
52
52
  "ssri": "^11.0.0",
53
53
  "tar": "^6.2.1",
54
54
  "temp-dir": "^3.0.0",
55
- "tinyglobby": "^0.2.10",
55
+ "tinyglobby": "^0.2.11",
56
56
  "tinyrainbow": "^2.0.0"
57
57
  },
58
- "gitHead": "4d410a9f9e51771deb9f13e8af6fa8c0d2b698b2"
58
+ "gitHead": "50da3e58f5cdc17884b9be579da112fd311aaac0"
59
59
  }