refactor: Bump semantic-release from 25.0.3 to 25.0.8

[mtrezza]

Closes #270

Summary

Bumps the direct devDependency semantic-release from 25.0.3 to 25.0.8.

Details

• Routine patch-range bump of a build/release tooling devDependency.
• package.json and package-lock.json updated; lockfile churn is confined to the semantic-release entry (lockfileVersion preserved at 3).
• Replaces the Dependabot PR refactor: Bump semantic-release from 25.0.3 to 25.0.8 #270 so the commit is authored under the maintainer identity.

Summary by CodeRabbit

• Chores
  • Updated the automated release tooling dependency to version 25.0.8 to improve release management reliability.

[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: Pro

Run ID: 63fce930-c4f9-4cc0-90a8-198298b74ece

📥 Commits

Reviewing files that changed from the base of the PR and between 71e706c and 9f4673b.

📒 Files selected for processing (2)

• package-lock.json
• package.json

🚧 Files skipped from review as they are similar to previous changes (2)

• package.json
• package-lock.json

---

📝 Walkthrough

Walkthrough

Updates the semantic-release development dependency from 25.0.3 to 25.0.8 in package.json and synchronizes the corresponding lockfile metadata.

Changes

semantic-release update

Layer / File(s)	Summary
Align semantic-release dependency metadata package.json, package-lock.json	Updates the declared and installed semantic-release version to 25.0.8, including the lockfile URL and integrity hash.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 7

✅ Passed checks (7 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly matches the dependency bump and uses an allowed prefix.
Description check	✅ Passed	It includes the issue reference and a clear summary/details, though it does not follow the template headings exactly.
Linked Issues check	✅ Passed	The change fulfills #270 by upgrading semantic-release from 25.0.3 to 25.0.8 in package.json and the lockfile.
Out of Scope Changes check	✅ Passed	No unrelated code changes are present; the PR is limited to the semantic-release version bump.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Security Check	✅ Passed	Only semantic-release was bumped to 25.0.8; no code changed, and the release notes list security-hardening bug fixes.
Engage In Review Feedback	✅ Passed	PR shows “No reviews” and 0 participants; only bot comments exist, so there was no review feedback to ignore or resolve.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{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 100.00%. Comparing base (ecdd7b4) to head (9f4673b).

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #272   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            4         4           
  Lines          159       159           
=========================================
  Hits           159       159           

☔ 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.