Bump release-drafter/release-drafter from 5.23.0 to 6.0.0

[dependabot]

Bumps release-drafter/release-drafter from 5.23.0 to 6.0.0.

Release notes

Sourced from release-drafter/release-drafter's releases.

v6.0.0

What's Changed

• Update Node.js to 20 (#1379) @​massongit

Full Changelog: release-drafter/release-drafter@v5.25.0...v6.0.0

v6.0.0-beta.1

Prerelease of v6, first release of the CLI, feel free to provide feedback in the pull request: release-drafter/release-drafter#1204

v5.25.0

What's Changed

New

• add prerelease increment behavior (#1303) @​neilime
• add latest input (#1348) @​o-mago

Full Changelog: release-drafter/release-drafter@v5.24.0...v5.25.0

v5.24.0

What's Changed

New

• Add release version to github action output (#1300) @​mehdihadeli

Bug Fixes

• fix(release): strip prefix before comparing version (#1255) @​neilime

Full Changelog: release-drafter/release-drafter@v5.23.0...v5.24.0

Commits

• 3f0f870 v6.0.0
• 80296b4 Update Node.js to 20 (#1379)
• 09c613e v5.25.0
• 576ba52 feat: add prerelease increment behavior (#1303)
• ff929b5 feat: add latest input (#1348)
• 65c5fb4 v5.24.0
• 918b32f feat: add outputs descriptions to action.yaml file (#1347)
• a04b609 Add release version to github action output (#1300)
• b853a4c fix(release): strip prefix before comparing version (#1255)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Summary by Sourcery

Bump the release-drafter GitHub Action to version 6.0.0 in the release workflow to incorporate the latest features and improvements.

Build:

• Update release-drafter GitHub Action from version 5.23.0 to 6.0.0 in the release workflow configuration.

[semanticdiff-com]

Review changes with SemanticDiff.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates the release-drafter/release-drafter action from version 5.23.0 to 6.0.0 in the release workflow. The update primarily involves upgrading the Node.js runtime to version 20.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Update release-drafter/release-drafter action to version 6.0.0	Bump release-drafter/release-drafter from 5.23.0 to 6.0.0 Update Node.js runtime to version 20	.github/workflows/release.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, dependabot[bot]!). We assume it knows what it's doing!

[codiumai-pr-agent-free]

CI Failure Feedback 🧐

(Checks updated until commit 9a4e646)

Action: tests 3.9 / ubuntu-latest

Failed stage: Upgrade pip [❌]

Failure summary: The action failed because it could not open the requirements file. The file '.github/workflows/constraints.txt' is missing or not found in the specified directory.

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 201: PRE_COMMIT_COLOR: always 202: pythonLocation: /opt/hostedtoolcache/Python/3.9.20/x64 203: PKG_CONFIG_PATH: /opt/hostedtoolcache/Python/3.9.20/x64/lib/pkgconfig 204: Python_ROOT_DIR: /opt/hostedtoolcache/Python/3.9.20/x64 205: Python2_ROOT_DIR: /opt/hostedtoolcache/Python/3.9.20/x64 206: Python3_ROOT_DIR: /opt/hostedtoolcache/Python/3.9.20/x64 207: LD_LIBRARY_PATH: /opt/hostedtoolcache/Python/3.9.20/x64/lib 208: ##[endgroup] 209: �[31mERROR: Could not open requirements file: [Errno 2] No such file or directory: '.github/workflows/constraints.txt'�[0m�[31m 210: �[0m 211: ##[error]Process completed with exit code 1.

---

✨ CI feedback usage guide:

---

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

• Failed stage
• Failed test name
• Failure summary
• Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

• enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
• excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
• enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
• persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
• final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.