Update dependency @semantic-release/gitlab to v13

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@semantic-release/gitlab	^12.0.3 -> ^13.0.0

---

Release Notes

semantic-release/gitlab (@​semantic-release/gitlab)

v13.2.1

Compare Source

Bug Fixes

• assets: changed generation of gitlab release asset url when providing file assets with target project_upload to point to url for the uploaded file (56edd34), closes #​753

v13.2.0

Compare Source

Features

• commenting: disable if set to false (05d1a59)
• fail-comment: allow to skip based on provided condition #​480 #​636 (29b2a3a)
• success-comment: allow to skip based on provided condition #​480 #​636 (c402511)

v13.1.0

Compare Source

Features

• improve output in case of errors during publish (d53f94c)

v13.0.4

Compare Source

Bug Fixes

• get rid of import assertion (94cc869)

v13.0.3

Compare Source

Bug Fixes

• fail: properly parse issue creation response to log in terminal (4014f51)

v13.0.2

Compare Source

Bug Fixes

• deps: update dependency got to v14 (7e649eb)

v13.0.1

Compare Source

Bug Fixes

• deps: update dependency parse-url to v9 (4c4e342)

v13.0.0

Compare Source

chore

• bump minimum Node version to 20.8.1 (cf97c59)

BREAKING CHANGES

• Node 18 and 19 are not supported anymore. Users have to upgrade to Node 20.8.1 or later.

v12.1.1

Compare Source

Bug Fixes

• deps: update dependency globby to v14 (#​631) (9603edb)

v12.1.0

Compare Source

Features

• templating of path (e529aed)

v12.0.6

Compare Source

Bug Fixes

• deps: update dependency aggregate-error to v5 (#​597) (bf1b490)

v12.0.5

Compare Source

Bug Fixes

• use project path for API calls again (#​580) (b0357dc)

v12.0.4

Compare Source

Bug Fixes

• use numeric project ID for API calls (3350152)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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]

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.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

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>.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @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.

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 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]

🦙 MegaLinter status: ❌ ERROR

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ EDITORCONFIG	editorconfig-checker	2		0	0.01s
✅ JSON	jsonlint	2		0	0.21s
✅ JSON	npm-package-json-lint	yes		no	0.41s
✅ JSON	v8r	2		0	13.08s
✅ REPOSITORY	checkov	yes		no	11.67s
✅ REPOSITORY	gitleaks	yes		no	0.12s
✅ REPOSITORY	git_diff	yes		no	0.01s
✅ REPOSITORY	grype	yes		no	11.63s
✅ REPOSITORY	secretlint	yes		no	0.77s
✅ REPOSITORY	trivy-sbom	yes		no	1.38s
❌ SPELL	lychee	2		2	3.13s

See detailed report in MegaLinter reports
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

MegaLinter is graciously provided by