Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump the actions group across 1 directory with 3 updates #22

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 10, 2025

Bumps the actions group with 3 updates in the / directory: anchore/sbom-action, sigstore/cosign-installer and tenable/terrascan-action.

Updates anchore/sbom-action from 0.14.3 to 0.18.0

Release notes

Sourced from anchore/sbom-action's releases.

v0.18.0

Changes in v0.18.0

v0.17.9

Changes in v0.17.9

v0.17.8

Changes in v0.17.8

v0.17.7

Changes in v0.17.7

v0.17.6

Changes in v0.17.6

v0.17.5

Changes in v0.17.5

v0.17.4

Changes in v0.17.4

v0.17.3

Changes in v0.17.3

v0.17.2

Changes in v0.17.2

v0.17.1

Changes in v0.17.1

... (truncated)

Commits
  • f325610 chore(deps): bump peter-evans/create-pull-request from 7.0.5 to 7.0.6 (#511)
  • 83a99f5 chore(deps): bump release-drafter/release-drafter from 6.0.0 to 6.1.0 (#512)
  • 9af714f chore(deps): update Syft to v1.19.0 (#513)
  • df80a98 chore(deps): update Syft to v1.18.1 (#510)
  • 33651ab chore(deps): update Syft to v1.18.0 (#509)
  • a5bbe18 fix: github correlator name when run in matrix build (#482)
  • 55dc4ee chore(deps): update Syft to v1.17.0 (#507)
  • fc46e51 chore(deps): update Syft to v1.16.0 (#506)
  • 251a468 chore(deps): update Syft to v1.15.0 (#505)
  • 6bb446c chore(deps): bump actions/checkout from 4.2.1 to 4.2.2 (#504)
  • Additional commits viewable in compare view

Updates sigstore/cosign-installer from 3.1.1 to 3.8.0

Release notes

Sourced from sigstore/cosign-installer's releases.

v3.8.0

What's Changed

Full Changelog: sigstore/cosign-installer@v3...v3.8.0

v3.7.0

What's Changed

Full Changelog: sigstore/cosign-installer@v3.6.0...v3.7.0

v3.6.0

What's Changed

Full Changelog: sigstore/cosign-installer@v3...v3.6.0

v3.5.0

What's Changed

Full Changelog: sigstore/cosign-installer@v3.4.0...v3.5.0

v3.4.0

What's Changed

New Contributors

Full Changelog: sigstore/cosign-installer@v3...v3.4.0

... (truncated)

Commits
  • c56c2d3 Bump actions/setup-go from 5.2.0 to 5.3.0 (#180)
  • 02e36b8 bump for cosign v2.4.2 release (#181)
  • 789d288 test action against all non-rc releases, verify entry in rekor log (#179)
  • e11c089 Bump actions/setup-go from 5.1.0 to 5.2.0 (#178)
  • 718228a Bump actions/setup-go from 5.0.2 to 5.1.0 (#176)
  • 325063e Bump actions/checkout from 4.2.1 to 4.2.2 (#177)
  • b929758 Bump actions/checkout from 4.2.0 to 4.2.1 (#175)
  • dc72c7d bump for latest cosign v2.4.1 release (#173)
  • 08bb361 Bump actions/checkout from 4.1.7 to 4.2.0 (#172)
  • 4959ce0 update readme for new release (#170)
  • Additional commits viewable in compare view

Updates tenable/terrascan-action from 1.4.1 to 1.5.0

Commits
  • dd7e921 Merge pull request #70 from tenable/dependabot/docker/tenable/terrascan-1.16.0
  • 460f876 Bump tenable/terrascan from 1.15.0 to 1.16.0
  • 0261ed4 Merge pull request #67 from tenable/snyk-fix-3f0d8531b5550e8062201f7a502dcd81
  • d151339 fix: Dockerfile to reduce vulnerabilities
  • 627eca7 Merge pull request #61 from nasir-rabbani/main
  • ca43ff5 Merge pull request #60 from tenable/job-summary
  • 5edc53f corrected the sarif output flag
  • f526ded adds job summary to action
  • 73eca6a Merge pull request #58 from tenable/branding
  • 771b4dd Update references to Tenable
  • 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Summary by Sourcery

Update GitHub Actions: Upgrade anchore/sbom-action to 0.18.0, sigstore/cosign-installer to 3.8.0, and tenable/terrascan-action to 1.5.0.

CI:

  • Upgrade anchore/sbom-action from 0.14.3 to 0.18.0
  • Upgrade sigstore/cosign-installer from 3.1.1 to 3.8.0
  • Upgrade tenable/terrascan-action from 1.4.1 to 1.5.0

Bumps the actions group with 3 updates in the / directory: [anchore/sbom-action](https://github.com/anchore/sbom-action), [sigstore/cosign-installer](https://github.com/sigstore/cosign-installer) and [tenable/terrascan-action](https://github.com/tenable/terrascan-action).


Updates `anchore/sbom-action` from 0.14.3 to 0.18.0
- [Release notes](https://github.com/anchore/sbom-action/releases)
- [Changelog](https://github.com/anchore/sbom-action/blob/main/RELEASE.md)
- [Commits](anchore/sbom-action@v0.14.3...f325610)

Updates `sigstore/cosign-installer` from 3.1.1 to 3.8.0
- [Release notes](https://github.com/sigstore/cosign-installer/releases)
- [Commits](sigstore/cosign-installer@v3.1.1...c56c2d3)

Updates `tenable/terrascan-action` from 1.4.1 to 1.5.0
- [Release notes](https://github.com/tenable/terrascan-action/releases)
- [Commits](tenable/terrascan-action@v1.4.1...v1.5.0)

---
updated-dependencies:
- dependency-name: anchore/sbom-action
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: actions
- dependency-name: sigstore/cosign-installer
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: actions
- dependency-name: tenable/terrascan-action
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: actions
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Feb 10, 2025
Copy link

sourcery-ai bot commented Feb 10, 2025

Reviewer's Guide by Sourcery

This PR updates three GitHub actions used in multiple workflow files. It bumps anchore/sbom-action/download-syft from v0.14.3 to v0.18.0, sigstore/cosign-installer from v3.1.1 (or v3.7.0 in some workflows) to v3.8.0, and tenable/terrascan-action from v1.4.1 to v1.5.0. These changes are applied across several workflow YAML files to ensure the latest improvements and fixes are integrated.

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

File-Level Changes

Change Details Files
Bump anchore/sbom-action/download-syft from v0.14.3 to v0.18.0
  • Updated the action reference SHA from 78fc58e... to f325610c9f50a54015d37c8d16cb3b0e2c8f4de0
  • Ensured consistency across multiple workflows using download-syft
.github/workflows/push-main-ui.yml
.github/workflows/release-ui.yml
.github/workflows/build-image-ui.yml
.github/workflows/push-main.yml
.github/workflows/release.yml
Bump sigstore/cosign-installer from v3.1.1/v3.7.0 to v3.8.0
  • Updated the action reference SHA from older revisions (6e04d228 or dc72c7d5) to c56c2d3e59e4281cc41dea2217323ba5694b171e
  • Applied the update across workflows that rely on cosign-installer for signing
.github/workflows/push-main-ui.yml
.github/workflows/release-ui.yml
.github/workflows/push-main.yml
.github/workflows/release.yml
Bump tenable/terrascan-action from v1.4.1 to v1.5.0
  • Updated the action version in terraform-plan.yml to use the v1.5.0 release
  • Reflected changes that include vulnerability fixes and improvements
.github/workflows/terraform-plan.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. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the 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 exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!
  • Generate a plan of action for an issue: Comment @sourcery-ai plan on
    an issue to generate a plan of action for it.

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

Copy link

coderabbitai bot commented Feb 10, 2025

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

Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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!

Copy link

codiumai-pr-agent-free bot commented Feb 10, 2025

CI Feedback 🧐

(Feedback updated until commit e4f9ef6)

A test triggered by this PR failed. Here is an AI-generated analysis of the failure:

Action: scan-terraform

Failed stage: Scan terrafrom code [❌]

Failure summary:

The action failed because Terrascan could not find the directory to scan. Specifically:

  • The specified directory path /home/runner/work/fanal/fanal/config/clusters does not exist
  • Terrascan was configured to scan Terraform files in this non-existent directory
  • This resulted in a runtime validation error and exit code 1

  • Relevant error logs:
    1:  ##[group]Operating System
    2:  Ubuntu
    ...
    
    138:  100 24.2M  100 24.2M    0     0  38.3M      0 --:--:-- --:--:-- --:--:--  281M
    139:  ##[group]Run terrascan scan -i terraform -d config/clusters -v \
    140:  �[36;1mterrascan scan -i terraform -d config/clusters -v \�[0m
    141:  �[36;1m    --skip-rules 'AC_AWS_0214,AC_AWS_0369,AC_AWS_0487,AC_AWS_078,AWS.CloudTrail.Logging.Medium.007,AC_AWS_0447,AC_AWS_0497,AC_AWS_0458,AC_AWS_0320'      �[0m
    142:  shell: /usr/bin/bash -e {0}
    143:  env:
    144:  GOROOT: /opt/hostedtoolcache/go/1.19.13/x64
    145:  ##[endgroup]
    146:  �[31merror�[0m	runtime/validate.go:86	directory '/home/runner/work/fanal/fanal/config/clusters' does not exist
    147:  �[31merror�[0m	cli/run.go:141	scan run failed{error 26 0  directory does not exist}
    148:  ##[error]Process completed with exit code 1.
    

    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    0 participants