[UPDATE] (deps): Bump actions/attest-build-provenance from 39cb715ce0ddd23df1f705e863f642bfb72dfb2b to 0e115cf485910f93daeddbda6d514da773493f27 in /.github/workflows

[dependabot]

Bumps actions/attest-build-provenance from 39cb715ce0ddd23df1f705e863f642bfb72dfb2b to 0e115cf485910f93daeddbda6d514da773493f27.

Changelog

Sourced from actions/attest-build-provenance's changelog.

Release Instructions

Follow the steps below to tag a new release for the actions/attest-build-provenance action.

If changes were made to the internal actions/attest-build-provenance/predicate action (any updates to ./predicate/action.yaml or any of the code in the https://github.com/actions/attest-build-provenance/blob/main/src directory), start with step #1; otherwise, skip directly to step #5.

1. Merge the latest changes to the main branch.

2. Create and push a new predicate tag of the form [email protected] following SemVer conventions:

   git tag -a "[email protected]" -m "[email protected] Release"
   git push --tags

3. Update the reference to the actions/attest-build-provenance/predicate action in action.yml to point to the SHA of the newly created tag.

4. Push the action.yml change and open a PR. Once it has been reviewed, merge the PR and proceed with the release instructions.

5. Create a new release for the top-level action using a tag of the form vX.X.X following SemVer conventions:

   gh release create vX.X.X

6. Move (or create) the major version tag to point to the same commit tagged above:

   git tag -fa vX -m "vX"
   git push origin vX --force

Commits

• 0e115cf Bump eslint-plugin-jest from 28.14.0 to 29.0.1 (#664)
• 1c9ec82 Bump the npm-development group with 2 updates (#665)
• f650dec update vulnerable deps (#663)
• 8827912 Bump jest and @​types/jest (#660)
• d3e91f0 Bump the npm-development group across 1 directory with 6 updates (#661)
• e71c40d Bump @​types/node from 22.15.29 to 24.0.1 (#657)
• e8998f9 bump actions/attest from 2.3.0 to 2.4.0 (#654)
• 11c67f2 Bump the npm-development group across 1 directory with 6 updates (#649)
• See full diff in compare view

You can trigger a rebase of this PR 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)

[deepsource-io]

Here's the code health analysis summary for commits bd23f96..122229d. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
Python	✅ Success		View Check ↗
Test coverage	⚠️ Artifact not reported	Timed out: Artifact was never reported	View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

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

---

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

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.

[reactive-firewall]

👎 This is already included and superseded by v2.0.9a7