chore(deps): update semantic-release monorepo (major) #279

renovate · 2024-01-13T20:46:27Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@semantic-release/github	`^9.0.0` -> `^11.0.0`
semantic-release	`^22.0.0` -> `^24.0.0`

Release Notes

semantic-release/github (@semantic-release/github)

`v11.0.0`

Compare Source

chore

update peer dependency for semantic-release (95c7cdd)

Code Refactoring

modify commit associatedPRs and relatedIssues label property data type. (718134a)

Features

integrate warn in fail script (7a9914a)
integrate warn in success script (792720d)

BREAKING CHANGES

the commit associatedPR and relatedIssues label prop is now an array of objects with more properties
the minimum required version of semantic-release to use
@semantic-release/github is now v24.1.0

`v10.3.5`

Compare Source

Bug Fixes

replace searchAPI usage with GraphQL in findSRIssue util (#907) (7fb46a3)

`v10.3.4`

Compare Source

`v10.3.3`

Compare Source

Bug Fixes

Revert: feat: verify OAuth scopes of classic GitHub PATs (#915) (990bd73)

`v10.3.2`

Compare Source

Bug Fixes

missing "PullRequest".canBeRebased field on GHES graphql api (#913) (4393578)

`v10.3.1`

Compare Source

Bug Fixes

max_node_limit_exceeded error when fetching associatedPRs (#912) (bb806af)

`v10.3.0`

Compare Source

Features

allow conditional skip on success and fail comments (#874) (e097d1c)

`v10.2.0`

Compare Source

Features

verify OAuth scopes of classic GitHub PATs (#897) (be071a2)

`v10.1.7`

Compare Source

Bug Fixes

ignore case when checking for repo rename (#903) (2b1b9b6), closes #901

`v10.1.6`

Compare Source

`v10.1.5`

Compare Source

Bug Fixes

compare only / when checking for rename (#886) (24ea2ee)

`v10.1.4`

Compare Source

Bug Fixes

docs: correct docs branch for fail-comment links (#893) (b591730)

`v10.1.3`

Compare Source

Bug Fixes

Revert "fix: failing release due to renamed repository (#878)" (#887) (325952e)

`v10.1.2`

Compare Source

Bug Fixes

failing release due to renamed repository (#878) (76fdaa3)

`v10.1.1`

Compare Source

Bug Fixes

invalid GraphQL query generated when no release commits are found (#876) (8ee2744)

`v10.1.0`

Compare Source

Features

use branch prerelease property for detection (#863) (45b8da9)

`v10.0.7`

Compare Source

Bug Fixes

replace github search api with graphql in success lifecycle method (#857) (be394cf)

`v10.0.6`

Compare Source

Bug Fixes

corrected homepage link in package.json so the generated links in the errors are valid (#848) (865762d)

`v10.0.5`

Compare Source

Bug Fixes

normalize GitHub API URL (#839) (1e66974)

`v10.0.4`

Compare Source

Bug Fixes

introduce dedicated option for GitHub API endpoint (#829) (908ff83)

`v10.0.3`

Compare Source

`v10.0.2`

Compare Source

Bug Fixes

deps: update octokit monorepo (major) (#792) (97e368d)

`v10.0.1`

Compare Source

Bug Fixes

deps: update dependency issue-parser to v7 (#798) (8140ba8)

`v10.0.0`

Compare Source

Features

node-versions: dropped support for node v18 and v19 (#797) (aea314f)

BREAKING CHANGES

node-versions: node v18 and v19 are no longer supported

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

`v24.2.0`

Compare Source

Features

clarify branch existence requirement in error messages (#3462) (05a2ea9)

`v24.1.3`

Compare Source

Bug Fixes

branch-naming: prevent non-range versions from being identified as maintenance branches (07f2672)

`v24.1.2`

Compare Source

Bug Fixes

deps: update @semantic-release/github to v11.0.0 (#3460) (43df51b)

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

`v23.1.1`

Compare Source

`v23.1.0`

Compare Source

`v23.0.8`

Compare Source

Bug Fixes

deps: rename read-pkg-up -> read-package-up (4980cba)
deps: rename read-pkg-up -> read-package-up (#3249) (95a8b9e)

`v23.0.7`

Compare Source

`v23.0.6`

Compare Source

Bug Fixes

deps: update dependency @semantic-release/release-notes-generator to v13 (#3237) (b7e08fc)

`v23.0.5`

Compare Source

`v23.0.4`

Compare Source

`v23.0.3`

Compare Source

`v23.0.2`

Compare Source

Bug Fixes

deps: update dependency marked to v12 (#3176) (38105f5)

`v23.0.1`

Compare Source

Bug Fixes

deps: update dependency marked-terminal to v7 (9faded8)

`v23.0.0`

Compare Source

Bug Fixes

deps: update dependency cosmiconfig to v9 (#3105) (07dde04)
deps: update dependency marked to v11 (#3079) (6d2a6f1)
deps: upgraded to the latest version of env-ci (0d0ed9d)
use one note reference per tag to prevent conflicts (#2085) (020ea7d)

Features

node-versions: dropped support for node v18 and raised the minimum for v20 (2904832), closes /github.com/semantic-release/gitlab/pull/647#discussion_r1423131205

BREAKING CHANGES

deps: woodpecker ci users need to upgrade to v1.0.0 or higher to remain supported. see
https://github.com/semantic-release/env-ci/releases/tag/v11.0.0 for more information
node-versions: support for node v18 has been dropped and the minimum for v20 is now v20.8.1

related to https://github.com/semantic-release/semantic-release/discussions/3088

deps: if using release.config.js as the name of your config file, it needs to be moved to a .config/ directory. see https://github.com/cosmiconfig/cosmiconfig/releases/tag/v9.0.0 for more detail

Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

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

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

renovate · 2024-01-13T20:46:28Z

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/semantic-release
npm ERR!   dev semantic-release@"^23.0.0" from the root project
npm ERR!   peer semantic-release@">=20.1.0" from @semantic-release/[email protected]
npm ERR!   node_modules/@semantic-release/commit-analyzer
npm ERR!     @semantic-release/commit-analyzer@"^11.0.0" from [email protected]
npm ERR!   3 more (@semantic-release/npm, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer semantic-release@"^22.0.5" from [email protected]
npm ERR! node_modules/gradle-semantic-release-plugin
npm ERR!   dev gradle-semantic-release-plugin@"^1.8.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/semantic-release
npm ERR!   peer semantic-release@"^22.0.5" from [email protected]
npm ERR!   node_modules/gradle-semantic-release-plugin
npm ERR!     dev gradle-semantic-release-plugin@"^1.8.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-03-15T01_17_56_421Z-debug-0.log

sonarcloud · 2024-01-13T20:47:42Z

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

sonarcloud · 2024-03-15T01:20:10Z

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

renovate · 2024-05-31T23:45:44Z

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/semantic-release
npm ERR!   dev semantic-release@"^24.0.0" from the root project
npm ERR!   peer semantic-release@">=20.1.0" from @semantic-release/[email protected]
npm ERR!   node_modules/@semantic-release/commit-analyzer
npm ERR!   3 more (@semantic-release/npm, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer semantic-release@"^22.0.5" from [email protected]
npm ERR! node_modules/gradle-semantic-release-plugin
npm ERR!   dev gradle-semantic-release-plugin@"^1.8.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/semantic-release
npm ERR!   peer semantic-release@"^22.0.5" from [email protected]
npm ERR!   node_modules/gradle-semantic-release-plugin
npm ERR!     dev gradle-semantic-release-plugin@"^1.8.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-09-24T20_16_52_520Z-debug-0.log

sonarcloud · 2024-05-31T23:48:03Z

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

sonarcloud · 2024-09-24T20:19:11Z

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from fb2812c to 27f5dbe Compare March 15, 2024 01:18

renovate bot changed the title ~~chore(deps): update dependency semantic-release to v23~~ chore(deps): update semantic-release monorepo (major) Mar 15, 2024

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 27f5dbe to feb3569 Compare May 31, 2024 23:45

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from feb3569 to 84e535e Compare September 9, 2024 11:53

chore(deps): update semantic-release monorepo

6691c4a

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 84e535e to 6691c4a Compare September 24, 2024 20:16

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update semantic-release monorepo (major) #279

chore(deps): update semantic-release monorepo (major) #279

renovate bot commented Jan 13, 2024 •

edited

Loading

renovate bot commented Jan 13, 2024 •

edited

Loading

sonarcloud bot commented Jan 13, 2024

sonarcloud bot commented Mar 15, 2024

renovate bot commented May 31, 2024 •

edited

Loading

sonarcloud bot commented May 31, 2024

sonarcloud bot commented Sep 24, 2024

chore(deps): update semantic-release monorepo (major) #279

Are you sure you want to change the base?

chore(deps): update semantic-release monorepo (major) #279

Conversation

renovate bot commented Jan 13, 2024 • edited Loading

Release Notes

chore

Code Refactoring

Features

BREAKING CHANGES

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Features

Features

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Features

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Features

BREAKING CHANGES

Features

Bug Fixes

Bug Fixes

Bug Fixes

BREAKING CHANGES

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Features

BREAKING CHANGES

Configuration

renovate bot commented Jan 13, 2024 • edited Loading

⚠ Artifact update problem

File name: package-lock.json

sonarcloud bot commented Jan 13, 2024

Quality Gate passed

sonarcloud bot commented Mar 15, 2024

Quality Gate passed

renovate bot commented May 31, 2024 • edited Loading

⚠️ Artifact update problem

File name: package-lock.json

sonarcloud bot commented May 31, 2024

Quality Gate passed

sonarcloud bot commented Sep 24, 2024

Quality Gate passed

renovate bot commented Jan 13, 2024 •

edited

Loading

renovate bot commented Jan 13, 2024 •

edited

Loading

renovate bot commented May 31, 2024 •

edited

Loading