refactor: Upgrade semantic-release from 19.0.3 to 25.0.3

[mtrezza]

Replaces #415

Summary

Upgrades semantic-release from 19.0.3 to 25.0.3 (major version bump). This is a replacement PR for the Dependabot PR because upgrading to semantic-release v25 also requires updating the Node.js version in the release workflow.

Changes

• package.json: Update semantic-release from 19.0.3 to 25.0.3
• package-lock.json: Regenerated lock file (sourced from Dependabot PR chore(deps): bump @tootallnate/once and semantic-release #415); also removes the no-longer-needed transitive dependency @tootallnate/once
• .github/workflows/release-automated.yml: Update Node.js version from 20 to 22 (semantic-release v25 requires Node.js ^22.14.0 || >= 24.10.0)

Compatibility

• All existing semantic-release plugins (@semantic-release/commit-analyzer@9, @semantic-release/release-notes-generator@10, @semantic-release/changelog@6, @semantic-release/exec@6, @semantic-release/git@10, @droidsolutions-oss/semantic-release-nuget@1.4.1, @droidsolutions-oss/semantic-release-update-file@1.4.0) declare semantic-release >= 18.0.0 as peer dependency, so they are compatible with v25
• The release.config.js uses CommonJS syntax (require(), module.exports), which remains compatible since the repo's package.json does not set "type": "module"

Node.js version progression across semantic-release majors

Version	Node.js requirement
v19	(current)
v20-v21	>= 18
v22	^18.17 || >= 20.6.1
v23-v24	>= 20.8.1
v25	^22.14.0 || >= 24.10.0

Note on CI

The .NET 8.0 and .NET 9.0 test failures are pre-existing on master (SSL/HTTP infrastructure issues unrelated to this change).

[parse-github-assistant]

I will reformat the title to use the proper commit message syntax.

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

[coderabbitai]

Warning

Rate limit exceeded

@mtrezza has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 13 minutes and 2 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 13 minutes and 2 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 95124020-0b85-4554-85fd-e18b93002907

📥 Commits

Reviewing files that changed from the base of the PR and between 7577f29 and 4f0d117.

📒 Files selected for processing (3)

• .github/workflows/release-automated.yml
• package-lock.json
• package.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[mtrezza]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.