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

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@semantic-release/changelog	^3.0.4 → ^7.0.0
@semantic-release/exec	^3.3.7 → ^7.0.0
@semantic-release/git	7.0.18 → 11.0.1

---

Release Notes

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

v7.0.0

Compare Source

Features

• ES Module (#​414) (e154214)

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/semantic-release#2133
• semantic-release/semantic-release#4032

v6.0.3

Compare Source

Bug Fixes

• deps: update dependency fs-extra to v11.1.1 (#​309) (47045b3)

v6.0.2

Compare Source

Bug Fixes

• deps: update dependency fs-extra to v11 (#​276) (404c768)

v6.0.1

Compare Source

Bug Fixes

• deps: update dependency @​semantic-release/error to v3 (#​167) (ef37296)

v6.0.0

Compare Source

Features

• node-version: raised the minimum required version to v14.17 (#​170) (5cf74e4)

BREAKING CHANGES

• node-version: the minimum required version of node is now v14.17

v5.0.1

Compare Source

Bug Fixes

• package: update fs-extra to version 9.0.0 (997fe15)

v5.0.0

Compare Source

chore

• require Node.js >=10.18 (5ffdf49)

BREAKING CHANGES

• Require Node.js >= 10.18

v4.0.0

Compare Source

Features

• require Node.js >=10.13 (1f483af)

BREAKING CHANGES

• Require Node.js >= 10.13

v3.0.6

Compare Source

Bug Fixes

• use correct peerDependencies for semantic-release (d36ee06)

v3.0.5

Compare Source

Bug Fixes

• require Node.js >=8.16 (efcc658)

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

• deps: update dependency @​semantic-release/error to v4 (#​353) (471f963)

v7.0.1

Compare Source

Bug Fixes

• deps: update dependency parse-json to v8 (#​394) (080440f)

v7.0.0

Compare Source

Features

• ES Module (#​411) (b4462db)

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)

v6.0.3

Compare Source

Bug Fixes

• typo in EINVALIDEXECCWD error message (#​209) (2d15fbd)

v6.0.2

Compare Source

Bug Fixes

• deps: update dependency @​semantic-release/error to v3 (#​185) (f690867)

v6.0.1

Compare Source

Bug Fixes

• deps: update dependency execa to v5 (#​127) (2b7163e)

v6.0.0

Compare Source

Features

• node-version: raised the minimum required version to v14.17 (#​188) (020eab0)

BREAKING CHANGES

• node-version: the minimum required version of node is now v14.17

v5.0.0

Compare Source

chore

• require Node.js >=10.18 (5984b6e)

BREAKING CHANGES

• Require Node.js >= 10.18

v4.0.0

Compare Source

Bug Fixes

• package: update execa to version 4.0.0 (662a148)
• use correct peerDependencies for semantic-release (fda4ecf)
• package: update aggregate-error to version 2.0.0 (f18fbd4)
• package: update execa to version 2.0.2 (6579bb3)
• package: update execa to version 3.0.0 (ae40d3f)
• return false in addChannel if step is skipped (d12a029)
• return false in publish if package if step is skipped (48fc813)

Features

• add addChannel plugin step (bdeda6c)
• require Node.js >=10.13 (e4367de)
• require Node.js >=8.15 (454965e)

BREAKING CHANGES

• Require Node.js >= 10.13
• Require Node.js => 8.15

v3.3.8

Compare Source

Bug Fixes

• package: update execa to version 3.2.0 (1b89db4)
• require Node.js >=8.16 (e520840)

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

v11.0.1

Compare Source

Bug Fixes

• deps: update dependency execa to v10 (#​564) (b39d5c6)

v11.0.0

Compare Source

Features

• ES Module (#​544) (4d704a2), closes #​491 #​490

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: nyc → c8, added pretest, removed test:ci

Related Issue

• semantic-release/semantic-release#2133
• semantic-release/semantic-release#4032

v10.0.1

Compare Source

Bug Fixes

• deps: update dependency @​semantic-release/error to v3 (#​295) (3e934d4)

v10.0.0

Compare Source

Features

• node-version: raised the minimum required version to v14.17 (7ab65f8)

BREAKING CHANGES

• node-version: the minimum required version of node is now v14.17

v9.0.1

Compare Source

Bug Fixes

• deps: update dependency execa to v5 (#​228) (f536d60)

v9.0.0

Compare Source

chore

• require Node.js >=10.18 (4016fcc)

BREAKING CHANGES

• Require Node.js >= 10.18

v8.0.0

Compare Source

Bug Fixes

• package: update execa to version 4.0.0 (9c1dc67)
• include deleted files in release commit (f59d20c)
• package: update aggregate-error to version 2.0.0 (3eb8f60)
• package: update execa to version 2.0.2 (9404d44)
• package: update execa to version 3.0.0 (e6af5b4)
• look for modified fiels to commit only if there files matching the globs (d97c030)
• update globby to latest version (9e2b2e5)

Features

• require Node.js >=10.13 (81955b8)
• require Node.js >=8.15 (15356b1)
• support branch parameter from semantic-release@​16.0.0 (02b1f6d)

BREAKING CHANGES

• Require Node.js >= 10.13
• Require Git 2.7.1 or higher
• Require Node.js => 8.15

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
• 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.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​semantic-release/​exec@​3.3.7 ⏵ 7.1.0	+1
	@​semantic-release/​changelog@​3.0.4 ⏵ 7.0.0	+1		+3	+4
	@​semantic-release/​git@​7.0.18 ⏵ 11.0.1	+1			+11

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm execa is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: yarn.lock → npm/@semantic-release/exec@7.1.0 → npm/execa@9.6.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/execa@9.6.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report