Skip to content

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

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-semantic-release-monorepo
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-semantic-release-monorepo

Conversation

@renovate

@renovate renovate Bot commented Jun 4, 2024

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@semantic-release/changelog 6.0.37.0.0 age confidence
@semantic-release/exec 6.0.37.1.0 age confidence
@semantic-release/git 10.0.111.0.1 age confidence
@semantic-release/npm 12.0.213.1.5 age confidence
semantic-release 23.1.125.0.9 age confidence

Release Notes

semantic-release/changelog (@​semantic-release/changelog)

v7.0.0

Compare Source

Features
BREAKING CHANGES
  • @semantic-release/changelog is now a native ES
    Module. It has named exports for each plugin hook (verifyConditions,
    prepare)
  • the minimum required version of semantic-release to use
    @semantic-release/changelog is now
    v20.1.0
Other Notable Changes
  • Replaced xo with prettier with default configuration; following
    newly established convention
  • Replaced nyc with c8 for code coverage
  • Replaced lodash with lodash-es for proper esm support
Related Issue
semantic-release/exec (@​semantic-release/exec)

v7.1.0

Compare Source

Features
  • error: print more useful error for non-process failure (#​449) (a285bc5)

v7.0.3

Compare Source

Bug Fixes
  • deps: update dependency execa to v9 (643e2eb)

v7.0.2

Compare Source

Bug Fixes

v7.0.1

Compare Source

Bug Fixes

v7.0.0

Compare Source

Features
BREAKING CHANGES
  • the minimum required version of semantic-release to use @semantic-release/exec is now v24.1.0; the warn logger method/function is now available to use in plugin

  • @semantic-release/exec is now a native ES Module. It has named exports for each plugin hook (verifyConditions, analyzeCommits, verifyRelease, generateNotes, prepare, publish, addChannel, success, fail)

semantic-release/git (@​semantic-release/git)

v11.0.1

Compare Source

Bug Fixes

v11.0.0

Compare Source

Features
BREAKING CHANGES
  • @semantic-release/git is now a native ES Module. It
    has named exports for each plugin hook (verifyConditions, prepare)
  • the minimum required version of semantic-release to use
    @semantic-release/git is now v20.1.0
Other Notable Changes
  • @semantic-release/error ^3^4 (ESM-only)
  • aggregate-error ^3^5 (ESM-only, uses native AggregateError)
  • execa ^5^9 (ESM-only, named export)
  • p-reduce ^2^3 (ESM-only)
  • Removed CJS-only devDeps: clear-module, file-url, fs-extra,
    get-stream, nyc
  • Added c8 for coverage; bumped ava, sinon, tempy,
    semantic-release, prettier
  • Engine: ^22.22.2 || >= 24.15;
  • Scripts: nycc8, added pretest, removed test:ci
Related Issue
semantic-release/npm (@​semantic-release/npm)

v13.1.5

Compare Source

Bug Fixes

v13.1.4

Compare Source

Bug Fixes

v13.1.3

Compare Source

Bug Fixes

v13.1.2

Compare Source

Bug Fixes

v13.1.1

Compare Source

Bug Fixes
  • publish-dry-run: temporarily remove the addition of dry-running the publish step (30bd176)

v13.1.0

Compare Source

Features
  • trusted-publishing: verify auth, considering OIDC vs tokens from various registries (e3319f1), closes #​958
  • trusted-publishing: refine the messages for related errors (316ce21), closes #​958
  • trusted-publishing: make request to verify if OIDC token exchange can succeed (c80ecb0), closes #​958
  • trusted-publishing: pass id-token as bearer header for github actions (d83b727), closes #​958
  • trusted-publishing: pass id-token as bearer header for gitlab pipelines (6d1c3cf), closes #​958
  • trusted-publishing: handle failure to retrieve id-token in the context of github actions (b673257), closes #​958
  • auth-error: update messaging for auth failure to be less token specific (e24967d)
  • auth: attempt a dry-run publish to determine auth status (841dc67)
Bug Fixes
  • trusted-publishing: uri encode the package name for the token exchange request (3dd95d0), closes #​958
  • auth: throw appropriate error when auth context fails to enable publishing (f5c8d85)
  • auth: throw error if dry-run publish determines lack of auth (8f88e9d)
  • verify-auth: enable the publish dry-run to work for projects publishing from a sub-directory (e7d684c)

v13.0.0

Compare Source

Features
  • node-versions: drop support for node versions v20, v21, and v23
  • node-versions: raise the minimum node version requirement for the v24 range (935439e)
Bug Fixes
BREAKING CHANGES
  • node-versions: the minimum node version for the v24 range is now v24.10.0
  • deps: a minimum of node v22.14 is now required
semantic-release/semantic-release (semantic-release)

v25.0.9

Compare Source

Bug Fixes
  • do not expose the authenticated repository URL in EGITNOPERMISSION errors (#​4283) (8d905a5)

v25.0.8

Compare Source

Bug Fixes
  • handle potential null values in commit message and gitTags trimming (0a60004)
  • hide-sensitive: mask key/auth/webhook env vars (973d763)
  • mask sensitive environment variables and improve commit handling (#​4252) (1bfdc52)
  • prevent template evaluation syntax in branch expansion and tag formatting (f121540)

v25.0.7

Compare Source

Bug Fixes
  • argument Injection via repositoryUrl in package.json (#​4245) (c46dbda)

v25.0.6

Compare Source

Bug Fixes
  • ensure encoded secrets get masked (8e28dd3)

v25.0.5

Compare Source

Bug Fixes

v25.0.4

Compare Source

Bug Fixes
  • code-quality: add missing comma in context object for consistency (493d6cd)

v25.0.3

Compare Source

Bug Fixes

v25.0.2

Compare Source

Bug Fixes

v25.0.1

Compare Source

Bug Fixes

v25.0.0

Compare Source

Bug Fixes
  • deps: update dependency hosted-git-info to v9 (9fa04f8)
  • deps: update dependency yargs to v18 (#​3745) (cde9a72)
  • deps: update to the stable version of the github plugin (f12cf81)
  • deps: update to the stable version of the release-notes-generator plugin (d9def72)
  • deps: updated to the stable version of the commit-analyzer plugin (291533b)
  • deps: upgrade to the new major version of the npm plugin, which upgrades npm to v11 for publishing (1be8290)
Features
  • node-versions: drop support for node versions v20, v21, and v23 (56d16f4)
  • node-versions: raise the minimum node version for the v24 range (116a188)
BREAKING CHANGES
  • node-versions: the minimum node version for the v24 range is now v24.10.0
  • node-versions: a minimum of node v22.14 is now required

v24.2.9

Compare Source

Bug Fixes

v24.2.8

Compare Source

Bug Fixes

v24.2.7

Compare Source

Performance Improvements

v24.2.6

Compare Source

Bug Fixes

v24.2.5

Compare Source

Bug Fixes
  • deps: raise the minimum of the defined range for marked-terminal (#​3742) (fb1ccd4)

v24.2.4

Compare Source

Bug Fixes

v24.2.3

Compare Source

Bug Fixes

v24.2.2

Compare Source

Bug Fixes

v24.2.1

Compare Source

Bug Fixes

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

v24.1.1

Compare Source

Bug Fixes

v24.1.0

Compare Source

Features

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

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "before 2am"
  • 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
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 2640062 to 06a7805 Compare June 12, 2024 00:22
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 18f416f to 24da4d8 Compare July 17, 2024 03:20
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 24da4d8 to d55b6cc Compare July 26, 2024 04:16
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from d8c19fc to fc8c9c1 Compare August 14, 2024 01:27
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from fc8c9c1 to 85bf343 Compare September 1, 2024 11:07
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from edc393a to 449735e Compare September 12, 2024 04:39
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from c6c08d0 to ad4197f Compare September 24, 2024 04:08
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from ad4197f to 8781227 Compare September 27, 2024 18:20
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 80323ce to 9fad595 Compare October 18, 2024 23:38
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 9fad595 to c887ca6 Compare October 25, 2024 21:41
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from c887ca6 to 3bac20b Compare November 17, 2024 00:47
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 3e51996 to 859361d Compare December 4, 2024 01:20
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 859361d to 1f37cbf Compare December 6, 2024 04:56
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 1f37cbf to 2ffa866 Compare December 18, 2024 01:11
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 2ffa866 to 83d0dee Compare January 3, 2025 08:05
@renovate renovate Bot changed the title chore(deps): update dependency semantic-release to v24 chore(deps): update semantic-release monorepo (major) Feb 1, 2025
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 1b6a48c to 32d8c37 Compare February 3, 2025 13:47
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 32d8c37 to 4c40fcf Compare February 9, 2025 16:54
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 7b2462c to 2a9c2a6 Compare August 13, 2025 13:55
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 2a9c2a6 to 52f76f8 Compare August 19, 2025 19:36
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 52f76f8 to 03f654a Compare August 30, 2025 15:11
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 03f654a to 7361c93 Compare August 30, 2025 15:19
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 137fe83 to 8e438fb Compare August 31, 2025 13:42
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 8e438fb to bb99e10 Compare September 10, 2025 21:27
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 1ff243d to eeef867 Compare September 25, 2025 16:59
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch 5 times, most recently from b282852 to a44b8ac Compare October 19, 2025 21:30
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from a44b8ac to 5d6f012 Compare October 21, 2025 18:07
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from f418193 to 2505a09 Compare November 10, 2025 18:06
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 20103e7 to ccde6a7 Compare November 19, 2025 00:00
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from ccde6a7 to fd4d9d9 Compare November 22, 2025 05:15
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from fd4d9d9 to db5e5d4 Compare December 3, 2025 19:33
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from db5e5d4 to 286f7a2 Compare December 12, 2025 21:34
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 286f7a2 to 9486683 Compare January 8, 2026 17:32
@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from f70b489 to 79570a0 Compare January 23, 2026 18:15
@renovate

renovate Bot commented Sep 15, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ 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 warn cli npm v12.0.2 does not support Node.js v20.20.2. This version of npm supports the following node versions: `^22.22.2 || ^24.15.0 || >=26.0.0`. You can find the latest version at https://nodejs.org/.
npm warn Unknown env config "store". This will error in a future major version of npm. See `npm help npmrc` for supported config options.
npm error code EALLOWREMOTE
npm error Fetching packages of type "remote" have been disabled
npm error Refusing to fetch "https://registry.npmjs.org/npm/-/npm-11.19.1.tgz"
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-09-15T18_32_57_624Z-debug-0.log

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