Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 25, 2025

This PR contains the following updates:

Package Change Age Confidence
lerna (source) ^8.1.8 -> ^8.2.4 age confidence

Release Notes

lerna/lerna (lerna)

v8.2.4

Compare Source

Bug Fixes
  • publish: ensure README file names are populated on package.json (#​4211) (362875d)
Features
  • support OIDC trusted publishing (d51e344)

OIDC trusted publishing is now supported by Lerna with no specification configuration required.

BREAKING CHANGES

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.

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.

  • node v18 support is dropped because it is end of life

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.

We strongly encourage all folks here to keep up with the maintenance LTS version of Node at an absolute minimum:

https://github.com/nodejs/release#release-schedule

The versions of node supported by lerna are now ^20.19.0 || ^22.12.0 || >=24.0.0.

If you are still using lerna add, lerna bootstrap or lerna link commands, please migrate to using your package manager's long-supported workspaces feature. The updated guide should help with this https://lerna.js.org/docs/legacy-package-management**

8.2.4 (2025-07-27)

Bug Fixes

8.2.3 (2025-06-29)

Bug Fixes
  • use internal fork of unmaintained strong-log-transformer (#​4195) (7115485)

8.2.2 (2025-04-10)

Note: Version bump only for package lerna

8.2.1 (2025-03-03)

Note: Version bump only for package lerna

v8.2.3

Compare Source

Bug Fixes
  • publish: ensure README file names are populated on package.json (#​4211) (362875d)
Features
  • support OIDC trusted publishing (d51e344)

OIDC trusted publishing is now supported by Lerna with no specification configuration required.

BREAKING CHANGES

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.

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.

  • node v18 support is dropped because it is end of life

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.

We strongly encourage all folks here to keep up with the maintenance LTS version of Node at an absolute minimum:

https://github.com/nodejs/release#release-schedule

The versions of node supported by lerna are now ^20.19.0 || ^22.12.0 || >=24.0.0.

If you are still using lerna add, lerna bootstrap or lerna link commands, please migrate to using your package manager's long-supported workspaces feature. The updated guide should help with this https://lerna.js.org/docs/legacy-package-management**

8.2.4 (2025-07-27)

Bug Fixes

8.2.3 (2025-06-29)

Bug Fixes
  • use internal fork of unmaintained strong-log-transformer (#​4195) (7115485)

8.2.2 (2025-04-10)

Note: Version bump only for package lerna

8.2.1 (2025-03-03)

Note: Version bump only for package lerna

v8.2.2

Compare Source

Bug Fixes
  • publish: ensure README file names are populated on package.json (#​4211) (362875d)
Features
  • support OIDC trusted publishing (d51e344)

OIDC trusted publishing is now supported by Lerna with no specification configuration required.

BREAKING CHANGES

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.

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.

  • node v18 support is dropped because it is end of life

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.

We strongly encourage all folks here to keep up with the maintenance LTS version of Node at an absolute minimum:

https://github.com/nodejs/release#release-schedule

The versions of node supported by lerna are now ^20.19.0 || ^22.12.0 || >=24.0.0.

If you are still using lerna add, lerna bootstrap or lerna link commands, please migrate to using your package manager's long-supported workspaces feature. The updated guide should help with this https://lerna.js.org/docs/legacy-package-management**

8.2.4 (2025-07-27)

Bug Fixes

8.2.3 (2025-06-29)

Bug Fixes
  • use internal fork of unmaintained strong-log-transformer (#​4195) (7115485)

8.2.2 (2025-04-10)

Note: Version bump only for package lerna

8.2.1 (2025-03-03)

Note: Version bump only for package lerna

v8.2.1

Compare Source

Bug Fixes
  • publish: ensure README file names are populated on package.json (#​4211) (362875d)
Features
  • support OIDC trusted publishing (d51e344)

OIDC trusted publishing is now supported by Lerna with no specification configuration required.

BREAKING CHANGES

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.

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.

  • node v18 support is dropped because it is end of life

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.

We strongly encourage all folks here to keep up with the maintenance LTS version of Node at an absolute minimum:

https://github.com/nodejs/release#release-schedule

The versions of node supported by lerna are now ^20.19.0 || ^22.12.0 || >=24.0.0.

If you are still using lerna add, lerna bootstrap or lerna link commands, please migrate to using your package manager's long-supported workspaces feature. The updated guide should help with this https://lerna.js.org/docs/legacy-package-management**

8.2.4 (2025-07-27)

Bug Fixes

8.2.3 (2025-06-29)

Bug Fixes
  • use internal fork of unmaintained strong-log-transformer (#​4195) (7115485)

8.2.2 (2025-04-10)

Note: Version bump only for package lerna

8.2.1 (2025-03-03)

Note: Version bump only for package lerna

v8.2.0

Compare Source

Bug Fixes
  • publish: ensure README file names are populated on package.json (#​4211) (362875d)
Features
  • support OIDC trusted publishing (d51e344)

OIDC trusted publishing is now supported by Lerna with no specification configuration required.

BREAKING CHANGES

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.

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.

  • node v18 support is dropped because it is end of life

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.

We strongly encourage all folks here to keep up with the maintenance LTS version of Node at an absolute minimum:

https://github.com/nodejs/release#release-schedule

The versions of node supported by lerna are now ^20.19.0 || ^22.12.0 || >=24.0.0.

If you are still using lerna add, lerna bootstrap or lerna link commands, please migrate to using your package manager's long-supported workspaces feature. The updated guide should help with this https://lerna.js.org/docs/legacy-package-management**

8.2.4 (2025-07-27)

Bug Fixes

8.2.3 (2025-06-29)

Bug Fixes
  • use internal fork of unmaintained strong-log-transformer (#​4195) (7115485)

8.2.2 (2025-04-10)

Note: Version bump only for package lerna

8.2.1 (2025-03-03)

Note: Version bump only for package lerna

v8.1.9

Compare Source

Bug Fixes
  • drop strip-ansi in favor of native stripVTControlCharacters (#​4095) (9e4ac9c)
Features

8.1.9 (2024-10-31)

Bug Fixes

8.1.8 (2024-08-05)

Bug Fixes

8.1.7 (2024-07-21)

Bug Fixes

8.1.6 (2024-07-05)

Bug Fixes

8.1.5 (2024-06-24)

Bug Fixes
  • update npm utility dependencies and related packages (#​4033) (bd1c2d8)

8.1.4 (2024-06-09)

Note: Version bump only for package lerna

8.1.3 (2024-05-13)

Bug Fixes

8.1.2 (2024-02-05)

Note: Version bump only for package lerna

8.1.1 (2024-02-05)

Note: Version bump only for package lerna


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot enabled auto-merge (squash) February 25, 2025 06:56
Copy link

coderabbitai bot commented Feb 25, 2025

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

cypress bot commented Feb 25, 2025

next-core    Run #11752

Run Properties:  status check passed Passed #11752  •  git commit 7bdad2ce67 ℹ️: Merge b0d894e240e51301ccf1888705d7f54a8dec4429 into f3386823e092033445871a2d5f7a...
Project next-core
Branch Review renovate/next-lerna-monorepo
Run status status check passed Passed #11752
Run duration 00m 27s
Commit git commit 7bdad2ce67 ℹ️: Merge b0d894e240e51301ccf1888705d7f54a8dec4429 into f3386823e092033445871a2d5f7a...
Committer renovate[bot]
View all properties for this run ↗︎

Test results
Tests that failed  Failures 0
Tests that were flaky  Flaky 0
Tests that did not run due to a developer annotating a test with .skip  Pending 0
Tests that did not run due to a failure in a mocha hook  Skipped 0
Tests that passed  Passing 17
View all changes introduced in this branch ↗︎

@renovate renovate bot force-pushed the renovate/next-lerna-monorepo branch 10 times, most recently from aa76b2a to c08e2a7 Compare March 3, 2025 16:14
@renovate renovate bot changed the title chore(deps): Update dependency lerna to ^8.2.0 (next) chore(deps): Update dependency lerna to ^8.2.1 (next) Mar 3, 2025
@renovate renovate bot force-pushed the renovate/next-lerna-monorepo branch 3 times, most recently from 0471f17 to 4e8ab39 Compare March 10, 2025 03:56
@renovate renovate bot force-pushed the renovate/next-lerna-monorepo branch 4 times, most recently from 2f1c2f1 to 20598dc Compare March 13, 2025 06:33
@renovate renovate bot force-pushed the renovate/next-lerna-monorepo branch 3 times, most recently from ea8af85 to eca978a Compare April 2, 2025 01:37
@renovate renovate bot force-pushed the renovate/next-lerna-monorepo branch 4 times, most recently from 141a729 to 61ae1b0 Compare April 10, 2025 19:48
@renovate renovate bot changed the title chore(deps): Update dependency lerna to ^8.2.1 (next) chore(deps): Update dependency lerna to ^8.2.2 (next) Apr 10, 2025
@renovate renovate bot force-pushed the renovate/next-lerna-monorepo branch from 61ae1b0 to e40ddbc Compare April 17, 2025 01:31
@renovate renovate bot force-pushed the renovate/next-lerna-monorepo branch 5 times, most recently from d0c6ac4 to ff86997 Compare June 29, 2025 20:55
@renovate renovate bot changed the title chore(deps): Update dependency lerna to ^8.2.2 (next) chore(deps): Update dependency lerna to ^8.2.3 (next) Jun 29, 2025
@renovate renovate bot force-pushed the renovate/next-lerna-monorepo branch from ff86997 to 2e86986 Compare July 22, 2025 12:43
@renovate renovate bot force-pushed the renovate/next-lerna-monorepo branch 4 times, most recently from 9bd6ccf to d96ec07 Compare August 10, 2025 13:37
@renovate renovate bot force-pushed the renovate/next-lerna-monorepo branch 4 times, most recently from 4eae329 to 5016e67 Compare August 15, 2025 01:34
@renovate renovate bot force-pushed the renovate/next-lerna-monorepo branch 7 times, most recently from 39750fb to af421c7 Compare September 2, 2025 09:24
@renovate renovate bot force-pushed the renovate/next-lerna-monorepo branch from af421c7 to 016b1d9 Compare September 8, 2025 01:46
@renovate renovate bot changed the title chore(deps): Update dependency lerna to ^8.2.3 (next) chore(deps): Update dependency lerna to ^8.2.4 (next) Sep 15, 2025
@renovate renovate bot force-pushed the renovate/next-lerna-monorepo branch from 016b1d9 to 0321c62 Compare September 15, 2025 11:12
@renovate renovate bot force-pushed the renovate/next-lerna-monorepo branch 2 times, most recently from fe51e7b to 8ba79c1 Compare September 28, 2025 08:06
@renovate renovate bot force-pushed the renovate/next-lerna-monorepo branch from 8ba79c1 to 276d6ef Compare October 9, 2025 06:43
@renovate renovate bot force-pushed the renovate/next-lerna-monorepo branch from 276d6ef to b0d894e Compare October 14, 2025 06:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants