moj-frontend build(deps): update semantic-release monorepo (major)

build(deps): update semantic-release monorepo (major)

Open renovate[bot] opened this issue 1 year ago • 0 comments

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@semantic-release/npm	`^11.0.0` -> `^12.0.0`
semantic-release	`^23.0.0` -> `^24.0.0`

Release Notes

semantic-release/npm (@semantic-release/npm)

`v12.0.1`

Compare Source

Bug Fixes

deps: update dependency execa to v9 (9ac5ed0)

`v12.0.0`

Compare Source

Features

exports: defined exports to point at ./index.js (9e193c2)
node-versions: dropped support for node v18 and v19 (2df962b)

BREAKING CHANGES

exports: exports has been defined, which prevents access to private apis (which arent intended for consumption anyway)
node-versions: node v18 and v19 are no longer supported

`v11.0.3`

Compare Source

Bug Fixes

deps: raised the minimum accepted range of npm to v10.5.0 (#759) (a0313f8), closes semantic-release/semantic-release#3202

even though our existing range allowed anyone to update as soon as the new npm version was available, this will encourage being on a version that does not report the ip vulnerability a bit more forcefully

semantic-release/semantic-release (semantic-release)

`v24.1.0`

Compare Source

`v24.0.0`

Compare Source

Bug Fixes

deps: upgraded to the beta of the commit-analyzer plugin (dfc3d91)
deps: upgraded to the beta of the release-notes-generator plugin (4a4cd92)

BREAKING CHANGES

deps: the commit-analyzer plugin now expects to be used with the latest major versions of conventional-changelog packages. if you are installing any of these packages in addition to semantic-release, be sure to update them as well
deps: the release-notes-generator plugin now expects to be used with the latest major versions of conventional-changelog packages. if you are installing any of these packages in addition to semantic-release, be sure to update them as well