Bump clechasseur/rs-cargo from 2.0.6 to 3.0.1

[dependabot]

Bumps clechasseur/rs-cargo from 2.0.6 to 3.0.1.

Release notes

Sourced from clechasseur/rs-cargo's releases.

v3.0.1

Fix version that properly supports using toolchain in combination with tool: cargo-hack.

What's Changed

• fix: proper support of toolchain with cargo-hack by @​clechasseur in clechasseur/rs-cargo#204

Full Changelog: clechasseur/rs-cargo@v3...v3.0.1

v3.0.0

New major release that introduces caching of non-cargo tools as well as support for installing and using cargo-hack.

Breaking change: the use-cross input has been removed and replaced by tool. If you update from a previous version, you will need to replace use-cross: true with tool: cross. See README for details.

What's Changed

• feat!: remove use-cross arg, replace with tool, add cargo-hack support by @​clechasseur in clechasseur/rs-cargo#201
• fix: sensible cache-key default by @​clechasseur in clechasseur/rs-cargo#203

Full Changelog: clechasseur/rs-cargo@v2...v3.0.0

Commits

• ba11837 fix: proper support of toolchain with cargo-hack (#204)
• 8653300 chore(deps): update dependency @​types/node to ^20.17.12 (#205)
• b711224 chore(deps): update typescript-eslint monorepo to ^8.19.1 (#206)
• 06e1355 fix: sensible cache-key default (#203)
• 289069a feat!: remove use-cross arg, replace with tool, add cargo-hack support ...
• aecb615 chore(deps): update dependency @​types/node to ^20.17.11 (#202)
• c2ff3ea chore(deps): update dependency typescript to ^5.7.2 (#195)
• 9664dcd chore(deps): update typescript-eslint monorepo to ^8.19.0 (#197)
• 8d0224a chore(deps): update dependency @​types/node to ^20.17.10 (#196)
• ffde69f chore(deps): update dependency prettier to ^3.4.2 (#198)
• Additional commits viewable 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)

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

---

Note

Free review on us!

CodeRabbit is offering free reviews until Wed Jan 15 2025 to showcase some of the refinements we've made.

🪧 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.
  • 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 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 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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.

[dryrunsecurity]

DryRun Security Summary

The code changes focus on enhancing the build, release, and publishing workflows for the Bulwark Rust-based security tool by updating dependencies, ensuring cross-platform builds, managing secure environment variables, and validating crate integrity while maintaining a strong application security posture.

Expand for full summary

Summary:

The provided code changes are focused on maintaining the build, release, and publishing workflows for the Bulwark application, which is a Rust-based security tool. The key changes include updating dependencies, ensuring cross-platform builds, managing secure environment variables, and validating the integrity of the published crates.

From an application security perspective, the changes follow good practices, such as:

1. Reviewing dependencies and actions used in the workflows to ensure they are secure and up-to-date.
2. Securely managing sensitive credentials (e.g., Crates.io registry token) using GitHub Secrets.
3. Limiting workflow execution to the official Bulwark repository to prevent potential abuse.
4. Validating the integrity of the generated crates before publishing them to the Crates.io registry.
5. Maintaining a comprehensive test suite to identify potential vulnerabilities.

Overall, the changes appear to be focused on improving the reliability and security of the Bulwark application's build and release processes, which is crucial for maintaining the application's overall security posture.

Files Changed:

1. .github/workflows/publish-release.yml: This workflow is responsible for publishing the Bulwark binaries to a GitHub release. The changes update the version of the clechasseur/rs-cargo GitHub Action used in the workflow, ensure cross-platform builds, and manage the artifact uploads.

2. .github/workflows/publish-crate.yml: This workflow publishes the Bulwark workspace of crates to the Crates.io registry. The changes update the clechasseur/rs-cargo action version, use secure environment variables for authentication, and validate the integrity of the generated crates.

3. .github/workflows/rust.yml: This workflow automates various Rust-related tasks, such as linting, running the Clippy tool, building documentation, and executing the test suite. The changes update the clechasseur/rs-cargo action version and ensure thorough testing of the Bulwark components.

Code Analysis

We ran 9 analyzers against 3 files and 0 analyzers had findings. 9 analyzers had no findings.

View PR in the DryRun Dashboard.