create-contentful-app
create-contentful-app copied to clipboard
chore(deps-dev): bump lerna from 6.6.2 to 7.0.0
Bumps lerna from 6.6.2 to 7.0.0.
Release notes
Sourced from lerna's releases.
7.0.0
7.0.0 (2023-06-08)
BREAKING CHANGES
After updating we strongly recommend running
lerna repair
in your project. This will migrate yourlerna.json
to the latest and greatest and remove any outdated options.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.
- legacy package management commands have been removed
We no longer include the
bootstrap
,add
, andlink
commands by default. We strongly recommend using your package manager (npm
,yarn
,pnpm
) for package management related concerns such as installing and linking dependencies.There will not be any active work done on these commands and you should look to migrate as soon as possible.
For full context how why we made this change and how you can migrate your projects, please read our detailed guide here: https://lerna.js.org/docs/legacy-package-management
- Workspaces are used by default and
useWorkspaces
has been removedWe now use your package manager's workspaces configuration by default in order to resolve packages for lerna to operate on. If you wish to customize the packages that lerna will operate on, you can still use a
packages
property in yourlerna.json
just as you did before, but there is no longer any need for auseWorkspaces
flag. If thepackages
property is present, lerna will use that, otherwise it will try and read your workspaces configuration.Running
lerna repair
will automatically removeuseWorkspaces
from yourlerna.json
for you.NOTE: If you are using
pnpm
as your package manager, it is important to set"npmClient": "pnpm"
in yourlerna.json
so that lerna knows to look for apnpm-workspaces.yaml
file and not just check your rootpackage.json
.
- lerna init can no longer be run on an existing lerna repo
It was a confusing behavior that
lerna init
could be run on an existing lerna repo and would attempt to coerce its setup to something closer to a fresh repo, so we have removed this behavior and lerna will hard error if it detects the directory is already initialized.You can run
lerna repair
at any time to update your configuration to the latest and greatest.
- long deprecated options have been removed
The following options (on the left of the => in each case) have been deprecated for many years (since before we took over stewardship of the project) and have finally been removed. If you are using them in your
lerna.json
all you need to do is runlerna repair
and it will automatically migrate you to their modern equivalent. If you are passing them in on the command line, you will need to update your usage as follows:
--includeFilteredDependencies
=>--includeDependencies
--includeFilteredDependents
=>--includeDependents
--githubRelease
=>--createRelease=github
--skipGit
=>--push=false --gitTagVersion=false
--repoVersion
=>[positional bump]
--cdVersion
=>[positional bump]
--npmTag
=>--distTag
--ignore
=>--ignoreChanges
Features
... (truncated)
Changelog
Sourced from lerna's changelog.
7.0.0 (2023-06-08)
Bug Fixes
- bump cosmiconfig to v8 (#3701) (898923d)
- internal cli.js should not be bundled (53d73c6)
- migration building/publishing issues (27bf800)
- publish: use correct version in log messages (#3702) (4be9188)
- support nx 16.3.1+ (#3707) (647dbb5)
Features
- add migration for adding $schema, increase some strictness (73ceac3)
7.0.0-alpha.8 (2023-06-07)
Bug Fixes
- bump cosmiconfig to v8 (#3701) (898923d)
- internal cli.js should not be bundled (53d73c6)
- migration building/publishing issues (27bf800)
- publish: use correct version in log messages (#3702) (4be9188)
- support nx 16.3.1+ (#3707) (647dbb5)
Features
- add migration for adding $schema, increase some strictness (73ceac3)
7.0.0-alpha.7 (2023-06-05)
Bug Fixes
- bump cosmiconfig to v8 (#3701) (898923d)
- internal cli.js should not be bundled (53d73c6)
- migration building/publishing issues (27bf800)
- publish: use correct version in log messages (#3702) (4be9188)
- support nx 16.3.1+ (#3707) (647dbb5)
Features
- add migration for adding $schema, increase some strictness (73ceac3)
7.0.0-alpha.6 (2023-06-02)
Bug Fixes
... (truncated)
Commits
3900fe9
chore(misc): publish 7.0.07307520
chore: release v7.0.0-alpha.85095b04
chore: deps updates (#3715)aca9efc
chore: deps updates (#3714)16df3e9
chore: deps updates (#3713)e7e0489
chore: rework publish directory and assets (#3711)d326fd7
chore: release v7.0.0-alpha.7fd57e02
chore: release v7.0.0-alpha.6a6be819
chore: docs updates647dbb5
fix: support nx 16.3.1+ (#3707)- Additional commits viewable in compare view
You can trigger a rebase of this PR by commenting @dependabot rebase
.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebase
will rebase this PR -
@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it -
@dependabot merge
will merge this PR after your CI passes on it -
@dependabot squash and merge
will squash and merge this PR after your CI passes on it -
@dependabot cancel merge
will cancel a previously requested merge and block automerging -
@dependabot reopen
will reopen this PR if it is closed -
@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Lerna doesn't handle dependency management anymore, so we must migrate to npm workspaces. Workspaces were introduced with npm 7. Node 14 only comes with npm 6. Therefore, we have to drop support for Node 14 in order to upgrade to lerna 7. Dropping support for Node 14 should be fine as it's EOL, but requires a separate PR as it's a breaking change.
A newer version of lerna exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged.
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version
or @dependabot ignore this minor version
. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore
condition with the desired update_types
to your config file.
If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
@dependabot ignore this major version
OK, I won't notify you about version 7.x.x again, unless you re-open this PR.