chore(deps): update dependency @octokit/request-error@>=1.0.0 <5.1.1 to v6

[renovate[bot]]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@octokit/request-error@>=1.0.0 <5.1.1	[>=5.1.1 -> >=6.1.8](https://renovatebot.com/diffs/npm/@octokit%2frequest-error@>=1.0.0 <5.1.1/5.1.1/6.1.8)

---

Release Notes

octokit/request-error.js (@​octokit/request-error@>=1.0.0 <5.1.1)

v6.1.8

Compare Source

Bug Fixes

• deps: update dependency @​octokit/types to v14 (#​505) (ab4ea7b)

v6.1.7

Compare Source

Bug Fixes

• ReDos regex vulnerability, reported by @​DayShift (d558320)

v6.1.6

Compare Source

Bug Fixes

• deps: bump @octokit/types to fix Deno compat (#​483) (e01d470)

v6.1.5

Compare Source

Bug Fixes

• types: add explicit | undefined to optional fields (#​462) (43fc3bd)

v6.1.4

Compare Source

Bug Fixes

• improve perf of request error instantiations (#​444) (ba04ffa)

v6.1.3

Compare Source

Bug Fixes

• docs: correct title in README (#​443) (e24d923)

v6.1.2

Compare Source

Bug Fixes

• ensure statusCode is always an integer (#​439) (6eb8634)

v6.1.1

Compare Source

Bug Fixes

• pkg: add default fallback and types export (#​419) (a1ab11e), closes octokit/core.js#665 octokit/core.js#667

v6.1.0

Compare Source

Features

• security: Add provenance (#​416) (2836ddb)

v6.0.3

Compare Source

Bug Fixes

• deps: update dependency @​octokit/types to v13 (352b655)

v6.0.2

Compare Source

Bug Fixes

• add main entry point (#​406) (4e55235), closes octokit/core.js#662

v6.0.1

Compare Source

Bug Fixes

• build: remove NodeJS/Browser specific builds (#​404) (479d0b4)

v6.0.0

Compare Source

Features

• v6 (#​401) (d73dee6)

BREAKING CHANGES

• remove code and headers properties that were previously deprecated
• switch package to ESM instead of CommonJS

---

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: Disabled by config. Please merge this manually once you are satisfied.

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

[coderabbitai[bot]]

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

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Join our Discord community for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions[bot]]

Thank you for following the naming conventions! 🙏

[pkg-pr-new[bot]]

Open in StackBlitz

@anolilab/multi-semantic-release

npm i https://pkg.pr.new/anolilab/semantic-release/@anolilab/multi-semantic-release@146

@anolilab/rc

npm i https://pkg.pr.new/anolilab/semantic-release/@anolilab/rc@146

@anolilab/semantic-release-clean-package-json

npm i https://pkg.pr.new/anolilab/semantic-release/@anolilab/semantic-release-clean-package-json@146

@anolilab/semantic-release-pnpm

npm i https://pkg.pr.new/anolilab/semantic-release/@anolilab/semantic-release-pnpm@146

@anolilab/semantic-release-preset

npm i https://pkg.pr.new/anolilab/semantic-release/@anolilab/semantic-release-preset@146

commit: 77effa2

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 64.55%. Comparing base (803cd12) to head (77effa2). Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #146   +/-   ##
=======================================
  Coverage   64.55%   64.55%           
=======================================
  Files          32       32           
  Lines         790      790           
  Branches      114      114           
=======================================
  Hits          510      510           
- Misses        277      280    +3     
+ Partials        3        0    -3     

Flag	Coverage Δ
rc	92.10% <ø> (ø)
semantic-release-clean-package-json	85.24% <ø> (ø)
semantic-release-pnpm	50.50% <ø> (ø)

see 1 file with indirect coverage changes

:rocket: New features to boost your workflow:

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

[socket-security[bot]]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	left-pad@​1.3.0

View full report

[github-actions[bot]]

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.