[mtrezza]

Closes #619

Changes

• 11.0.1: Updated the execa dependency from v9 to v10 (fix(deps): update dependency execa to v10 semantic-release/git#564). The plugin's Node.js engine range is unchanged from 11.0.0 (^22.22.2 || >=24.15); execa 10 requires Node.js 22, which is within that range. The plugin only runs in the release workflow on Node.js 24.
• Lock file: adds execa 10.1.1 and is-stream 4.0.1 nested under @semantic-release/git and the new execa dependency which-command 0.1.0; bumps the shared pretty-ms 9.3.0 to 9.3.1 and yoctocolors 2.1.1 to 2.2.0 to satisfy execa 10 (both still satisfy the existing execa 9 ranges). All are development-only.

Breaking Changes

None

Code Changes Required

None — the upgrade is a drop-in replacement.

Summary by CodeRabbit

• Chores
  • Updated the development tooling package to version 11.0.1.

[parse-github-assistant]

🚀 Thanks for opening this pull request! We appreciate your effort in improving the project. Please let us know once your pull request is ready for review.

Tip

• Keep pull requests small. Large PRs will be rejected. Break complex features into smaller, incremental PRs.
• Use Test Driven Development. Write failing tests before implementing functionality. Ensure tests pass.
• Group code into logical blocks. Add a short comment before each block to explain its purpose.
• We offer conceptual guidance. Coding is up to you. PRs must be merge-ready for human review.
• Our review focuses on concept, not quality. PRs with code issues will be rejected. Use an AI agent.
• Human review time is precious. Avoid review ping-pong. Inspect and test your AI-generated code.

Note

Please respond to review comments from AI agents just like you would to comments from a human reviewer. Let the reviewer resolve their own comments, unless they have reviewed and accepted your commit, or agreed with your explanation for why the feedback was incorrect.

Caution

Pull requests must be written using an AI agent with human supervision. Pull requests written entirely by a human will likely be rejected, because of lower code quality, higher review effort and the higher risk of introducing bugs. Please note that AI review comments on this pull request alone do not satisfy this requirement. Our CI and AI review are safeguards, not development tools. If many issues are flagged, rethink your development approach. Invest more effort in planning and design rather than using review cycles to fix low-quality code.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Essentials
• Run ID: ab524fbd-9616-46c7-b39e-cd04f9581f2d

📥 Commits

Reviewing files that changed from the base of the PR and between fc7348d and 54ba397.

📒 Files selected for processing: 2

• package-lock.json
• package.json

Included review availability: This review used your included allowance. 0 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 4 reviews per hour.

📝 Walkthrough

The development dependency @semantic-release/git is updated from 11.0.0 to 11.0.1. The lockfile records its updated execa dependency and related package resolution changes.

Changes: Semantic Release Git Dependency Update

Layer / File(s)	Summary
Dependency declaration and lockfile resolutions package.json, package-lock.json	The manifest updates @semantic-release/git to 11.0.1. The lockfile records execa 10.1.1 and is-stream 4.0.1, adds which-command, and updates pretty-ms and yoctocolors.

Priority: ➖ Normal

Estimated code review effort: 2 (Simple) | ~10 minutes

Merge Risk: ⚪ Minimal · up to 54ba3

This development-tooling update does not establish a blocked CI or release workflow. Node 20 may report engine warnings during installation, but no actionable merge risk remains.

Pre-merge checks: 7

Check name	Status	Explanation
Title check		The title uses the required refactor: prefix, capitalizes the first word after the prefix, and accurately describes the dependency upgrade.
Description check		The description clearly explains the dependency and lockfile updates, linked issue, runtime compatibility, breaking-change status, and required code changes. It does not use the repository template he…
Linked Issues check		Issue #619 requires upgrading @semantic-release/git from 11.0.0 to 11.0.1. package.json and both lockfile representations now select 11.0.1. The lockfile records the required execa ^10.0.0 dep…
Out of Scope Changes check		The changes remain within issue #619. They update the requested development dependency and the lockfile entries required by execa 10, including is-stream, which-command, pretty-ms, and `yoctoc…
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Security Check		The pull request changes only package.json and package-lock.json. It adds no application code, scripts, permissions, or input-handling logic. The new dependency entries are development-only, use H…
Engage In Review Feedback		PASS: The supplied review metadata reports no posted CodeRabbit review threads and zero actionable findings in the current review. Therefore, no review feedback existed that required engagement, imple…

Full details: Description check

Explanation

The description clearly explains the dependency and lockfile updates, linked issue, runtime compatibility, breaking-change status, and required code changes. It does not use the repository template headings or include the task checkboxes, but the content is mostly complete and directly related to the changes.

Full details: Linked Issues check

Explanation

Issue #619 requires upgrading @semantic-release/git from 11.0.0 to 11.0.1. package.json and both lockfile representations now select 11.0.1. The lockfile records the required execa ^10.0.0 dependency and its resolved transitive packages. No source or test changes are required for this dependency-only upgrade.

Full details: Out of Scope Changes check

Explanation

The changes remain within issue #619. They update the requested development dependency and the lockfile entries required by execa 10, including is-stream, which-command, pretty-ms, and yoctocolors. The diff contains no unrelated source, configuration, or public API changes.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.)

Full details: Security Check

Explanation

The pull request changes only package.json and package-lock.json. It adds no application code, scripts, permissions, or input-handling logic. The new dependency entries are development-only, use HTTPS npm registry URLs, and include integrity hashes. No git-based or insecure HTTP dependency source appears in the diff.

Full details: Engage In Review Feedback

Explanation

PASS: The supplied review metadata reports no posted CodeRabbit review threads and zero actionable findings in the current review. Therefore, no review feedback existed that required engagement, implementation, or discussion before resolution.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{Comment @coderabbitai help to get the list of available commands.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.18%. Comparing base (be3a7e8) to head (54ba397).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #625   +/-   ##
=======================================
  Coverage   99.18%   99.18%           
=======================================
  Files          11       11           
  Lines        1841     1841           
=======================================
  Hits         1826     1826           
  Misses         15       15           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[parseplatformorg]

🎉 This change has been released in version 8.5.7