Skip to content

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

Merged
laurenhitchon merged 1 commit into
mainfrom
renovate/major-semantic-release-monorepo
Jul 29, 2026
Merged

chore(deps): update semantic-release monorepo (major)#59
laurenhitchon merged 1 commit into
mainfrom
renovate/major-semantic-release-monorepo

Conversation

@renovate

@renovate renovate Bot commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@semantic-release/changelog ^6.0.3^7.0.0 age confidence
@semantic-release/git ^10.0.1^11.0.0 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/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

Configuration

📅 Schedule: (in timezone Australia/Sydney)

  • Branch creation
    • "before 7am on monday"
  • Automerge
    • At any time (no schedule defined)

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

Rebasing: Whenever PR is behind base branch, 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.

@DFSIdigital

DFSIdigital commented Jul 29, 2026

Copy link
Copy Markdown

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues
Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@renovate
renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch 4 times, most recently from 33a6a92 to 012eb73 Compare July 29, 2026 03:11
@laurenhitchon
laurenhitchon force-pushed the renovate/major-semantic-release-monorepo branch from 012eb73 to 6ad3935 Compare July 29, 2026 03:11
@renovate

renovate Bot commented Jul 29, 2026

Copy link
Copy Markdown
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@laurenhitchon
laurenhitchon merged commit 62118dc into main Jul 29, 2026
7 checks passed
@laurenhitchon
laurenhitchon deleted the renovate/major-semantic-release-monorepo branch July 29, 2026 03:17
laurenhitchon added a commit that referenced this pull request Jul 29, 2026
@semantic-release/changelog@7 and @semantic-release/git@11 (merged in #59)
declare engines "^22.22.2 || >=24.15". The repo's own floor was 24.0.0, so a
contributor on Node 24.0-24.14 satisfied package.json but hit a hard
EBADENGINE from engine-strict=true, reported against a transitive plugin
rather than repo policy. CI was never exposed: .nvmrc pins 24.16.0.

npm also pruned a stale extraneous conventional-commits-filter@6.0.1 entry
from the lockfile while rewriting the engines block.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants