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 anchore/sbom-action from 0.16.0 to 0.17.9 #16

Open
wants to merge 1 commit into
base: release/v1
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 16, 2024

Bumps anchore/sbom-action from 0.16.0 to 0.17.9.

Release notes

Sourced from anchore/sbom-action's releases.

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

v0.17.0

Changes in v0.17.0

... (truncated)

Commits
  • 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)
  • 1ca97d9 chore(deps): update Syft to v1.14.2 (#503)
  • 8d0a650 chore(deps): update Syft to v1.14.1 (#502)
  • f5e124a chore(deps): bump peter-evans/create-pull-request from 6.1.0 to 7.0.5 (#493)
  • Additional commits viewable in compare view

Dependabot compatibility score

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

Build:

  • Update anchore/sbom-action from version 0.16.0 to 0.17.9 in the GitHub Actions workflow.

Bumps [anchore/sbom-action](https://github.com/anchore/sbom-action) from 0.16.0 to 0.17.9.
- [Release notes](https://github.com/anchore/sbom-action/releases)
- [Changelog](https://github.com/anchore/sbom-action/blob/main/RELEASE.md)
- [Commits](anchore/sbom-action@e8d2a69...df80a98)

---
updated-dependencies:
- dependency-name: anchore/sbom-action
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Dec 16, 2024
Copy link

sourcery-ai bot commented Dec 16, 2024

Reviewer's Guide by Sourcery

This PR updates the anchore/sbom-action GitHub Action from version 0.16.0 to 0.17.9. The update includes multiple Syft dependency updates and minor improvements, with the main changes being version bumps for the underlying Syft tool (from v1.11.0 through v1.18.1) and a fix for GitHub correlator naming in matrix builds.

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

File-Level Changes

Change Details Files
Update of the SBOM action version in the GitHub workflow
  • Updated anchore/sbom-action from v0.16.0 to v0.17.9
  • Changed the commit hash reference from e8d2a6937ecead383dfe75190d104edd1f9c5751 to df80a981bc6edbc4e220a492d3cbe9f5547a6e75
.github/workflows/actions_release.yaml

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

Copy link
Contributor

coderabbitai bot commented Dec 16, 2024

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

CI Failure Feedback 🧐

Action: main / auto-merge / auto-merge

Failed stage: Run dependabot/[email protected] [❌]

Failure summary:

The action failed due to an authentication error (HTTP 401) when trying to fetch Dependabot
metadata. The GitHub token provided either:

  • Is invalid or expired
  • Lacks the required permissions to access the Dependabot API
  • Was not properly configured in the workflow

  • Relevant error logs:
    1:  ##[group]Operating System
    2:  Ubuntu
    ...
    
    36:  Uses: khulnasoft/actions/.github/workflows/job-auto-merge.yml@refs/heads/master (c912268be9a5c02f4921f45d4075a226f961a775)
    37:  Complete job name: main / auto-merge / auto-merge
    38:  ##[group]Run dependabot/[email protected]
    39:  with:
    40:  github-token: ***
    41:  skip-commit-verification: false
    42:  skip-verification: false
    43:  ##[endgroup]
    44:  ##[error]Api Error: (401) Bad credentials
    

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

    Copy link

    🦙 MegaLinter status: ❌ ERROR

    Descriptor Linter Files Fixed Errors Elapsed time
    ✅ REPOSITORY gitleaks yes no 3.87s
    ✅ REPOSITORY git_diff yes no 0.1s
    ❌ REPOSITORY grype yes 1 12.09s
    ✅ REPOSITORY secretlint yes no 3.13s
    ✅ REPOSITORY trivy-sbom yes no 0.97s
    ✅ REPOSITORY trufflehog yes no 5.15s
    ✅ YAML v8r 1 0 2.38s
    ❌ YAML yamllint 1 7 0.62s

    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 OX Security

    @dependabot dependabot bot changed the base branch from master to develop January 8, 2025 16:39
    @dependabot dependabot bot changed the base branch from develop to main January 13, 2025 12:41
    @dependabot dependabot bot changed the base branch from main to release/v1 January 22, 2025 02:48
    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