fix(deps): update dependency @anolilab/semantic-release-preset to v11.0.5

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@anolilab/semantic-release-preset (source)	11.0.4 -> 11.0.5

---

Release Notes

anolilab/semantic-release (@​anolilab/semantic-release-preset)

v11.0.5

Compare Source

Bug Fixes

• update package dependencies and configurations (d94ebd8)

Dependencies

• @​anolilab/semantic-release-clean-package-json: upgraded to 3.0.5
• @​anolilab/semantic-release-pnpm: upgraded to 2.0.5

---

Configuration

📅 Schedule: Branch creation - "after 10:00 before 19:00 every weekday except after 13:00 before 14:00" in timezone Europe/Berlin, 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.

---

Note

Upgrade @anolilab/semantic-release-preset to 11.0.5 and refresh related semantic-release dependencies in the lockfile.

• Monorepo config:
  • Bump @anolilab/semantic-release-preset in pnpm-workspace.yaml catalog to 11.0.5.
• Lockfile updates:
  • Update @anolilab/semantic-release-preset -> 11.0.5 and align transitive deps:
    • @semantic-release/npm -> 13.1.1 (from 12.0.2)
    • @semantic-release/github -> 12.0.2 (from 11.0.6)
    • @anolilab/semantic-release-clean-package-json -> 3.0.5 (from 3.0.4)
  • Adjust peer dependencies/engines and Octokit plugin versions; replace npm@10.9.3 with npm@11.6.2 entries.

^{Written by Cursor Bugbot for commit 81bee2d. This will update automatically on new commits. Configure here.}

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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

[github-actions]

Thank you for following the naming conventions! 🙏

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​anolilab/​semantic-release-preset@​11.0.4 ⏵ 11.0.5				+3
	eslint-plugin-validate-jsx-nesting@​0.1.1
	eslint-plugin-you-dont-need-lodash-underscore@​6.14.0
	eslint-plugin-yml@​1.19.0

View full report

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using our GitHub Discussions tab for questions.