chore(deps) Update dependency @semantic-release/exec to v7

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@semantic-release/exec	6.0.3 → 7.1.0

---

Release Notes

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)

---

Configuration

📅 Schedule: Branch creation - "before 10pm on Sunday" in timezone America/Chicago, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

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

[renovate]

⚠️ 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 unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: atlas-etl-crystal@1.1.50
npm ERR! Found: semantic-release@24.0.0
npm ERR! node_modules/semantic-release
npm ERR!   dev semantic-release@"24.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer semantic-release@">=24.1.0" from @semantic-release/exec@7.1.0
npm ERR! node_modules/@semantic-release/exec
npm ERR!   dev @semantic-release/exec@"7.1.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 /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2026-03-13T12_08_15_234Z-debug-0.log