You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- name: Stop all running agents for Nx Run Group ${{ env.NX_RUN_GROUP }}
48
+
- name: Stop all running agents
56
49
# It's important that we always run this step, otherwise in the case of any failures in preceding non-Nx steps, the agents will keep running and waste billable minutes
run: echo "NX_RUN_GROUP is ${{ env.NX_RUN_GROUP }}"
76
-
77
64
- name: Configure git metadata
78
65
run: |
79
66
git config --global user.email test@example.com
@@ -86,27 +73,19 @@ jobs:
86
73
run: npx nx-cloud start-agent
87
74
env:
88
75
NX_AGENT_NAME: ${{ matrix.agent }}
89
-
NX_RUN_GROUP: ${{ env.NX_RUN_GROUP }}
90
76
91
77
windows-main:
92
78
name: Nx Cloud - Windows Main Job
93
79
runs-on: windows-latest
94
80
env:
81
+
NX_CI_EXECUTION_ENV: "windows"
95
82
LERNA_OS_TYPE: windows
96
83
# Set the temp directory to a short dir without username in it otherwise import command specs have a problem because of different paths on windows agents
- name: Stop all running agents for Nx Run Group ${{ env.NX_RUN_GROUP }}
110
+
- name: Stop all running agents for Nx Run Group
132
111
# It's important that we always run this step, otherwise in the case of any failures in preceding non-Nx steps, the agents will keep running and waste billable minutes
133
112
if: ${{ always() }}
134
113
run: npx nx-cloud stop-all-agents
@@ -140,21 +119,14 @@ jobs:
140
119
matrix:
141
120
agent: [1, 2, 3, 4]
142
121
env:
122
+
NX_CI_EXECUTION_ENV: "windows"
143
123
LERNA_OS_TYPE: windows
144
124
# Set the temp directory to a short dir without containing username, otherwise import command specs have a problem because of different paths on windows agents
Copy file name to clipboardExpand all lines: CHANGELOG.md
+31Lines changed: 31 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,6 +3,37 @@
3
3
All notable changes to this project will be documented in this file.
4
4
See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
5
5
6
+
## BREAKING CHANGES
7
+
8
+
> After updating we strongly recommend running `lerna repair` in your project. This will migrate your `lerna.json` to the latest and greatest and remove any outdated options.
9
+
10
+
As this is a major release there are a few breaking changes to be aware of, which may or may not affect your lerna repos, depending on how you are using the tool.
11
+
12
+
-**node v16 support is dropped because it is end of life**
13
+
14
+
When a node version becomes end of life (EOL) it means that it does not receive any updates or maintenance whatsoever, even if critical security vulnerabilities have been uncovered.
15
+
16
+
We strongly encourage all folks here to keep up with the maintenance LTS version of Node at an absolute minimum:
-**lerna's task runner for `lerna run` now depends on nx v17 instead of v16**
21
+
22
+
`lerna run` gets to benefit from all of the further performance improvements in the nx v17 task runner behind scenes.
23
+
24
+
-**`@lerna/child-process` is no longer a separately published package**
25
+
26
+
Lerna is a monorepo management tool with versioning and publishing capabilities, it is not a child process manager. There are lots of good options out there in the ecosystem to help you with managing child processes in nodejs, and it does not really make sense to treat some of lerna's implementation details around child processes as if they were a public API. The package will be officially deprecated on npm in the future. You can of course take the code and fork it and adapt it for your own purposes if you wish!
27
+
28
+
-**Older packages under `@lerna/` on npm have been officially marked as deprecated**
29
+
30
+
Under prior stewardship the lerna repo used to publish a very large (>65) number of packages. The vast majority of these should not form part of the public API of lerna and so they have no longer been published as packages since v6. We have now officially marked them as deprecated packages on the npm registry so that users get clear feedback that they are using packages which are no longer maintained (which they can of course fork and do whatever they want with). NOTE: We have not yet marked `@lerna/child-process` as deprecated so as not to create noise for lerna v7 users until they have had chance to migrate to v8.
31
+
32
+
### Features
33
+
34
+
-**version:** add --premajor-version-bump option to force patch bumps for non-breaking changes in premajor packages ([#3876](https://github.com/lerna/lerna/issues/3876)) ([3b05947](https://github.com/lerna/lerna/commit/3b059476fd62fcb09ac391878b73640cceb6b5ef))
35
+
-**version:** use corepack for install when enabled ([#3877](https://github.com/lerna/lerna/issues/3877)) ([a3cb7ca](https://github.com/lerna/lerna/commit/a3cb7cad74266c74da5d005324bced500111ed1c))
-**version:** add --premajor-version-bump option to force patch bumps for non-breaking changes in premajor packages ([#3876](https://github.com/lerna/lerna/issues/3876)) ([3b05947](https://github.com/lerna/lerna/commit/3b059476fd62fcb09ac391878b73640cceb6b5ef))
0 commit comments