chore(deps): update anchore/sbom-action action to v0.20.5

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
anchore/sbom-action	action	minor	v0.15.1 -> v0.20.5

---

Release Notes

anchore/sbom-action (anchore/sbom-action)

v0.20.5

Compare Source

Changes in v0.20.5

• Update Syft to v1.31.0 (#​531)

v0.20.4

Compare Source

Changes in v0.20.4

• chore: update Syft to v1.29.0 (#​529)

v0.20.3

Compare Source

Changes in v0.20.3

• Fix: Strip emojis from correlator before using github APIs (#​527) [AndrewHendry]

v0.20.2

Compare Source

Changes in v0.20.2

• Update Syft to v1.28.0 (#​526)

v0.20.1

Compare Source

Changes in v0.20.1

• Update Syft to v1.27.1 (#​525)

v0.20.0

Compare Source

Changes in v0.20.0

• chore(deps): update Syft to v1.24.0 (#​522)

v0.19.0

Compare Source

Changes in v0.19.0

• chore(deps): update Syft to v1.23.0 (#​521)
• chore(deps): bump peter-evans/create-pull-request from 7.0.6 to 7.0.8 (#​519)
• chore(deps): bump cross-spawn (#​514)

v0.18.0

Compare Source

Changes in v0.18.0

• chore(deps): update Syft to v1.19.0 (#​513)
  • See Syft changelog for latest changes

v0.17.9

Compare Source

Changes in v0.17.9

• chore(deps): update Syft to v1.18.1 (#​510) [anchore-actions-token-generator]
• chore(deps): update Syft to v1.18.0 (#​509) [anchore-actions-token-generator]

v0.17.8

Compare Source

Changes in v0.17.8

• chore(deps): update Syft to v1.17.0 (#​507) [anchore-actions-token-generator]

v0.17.7

Compare Source

Changes in v0.17.7

• chore(deps): update Syft to v1.16.0 (#​506) [anchore-actions-token-generator]

v0.17.6

Compare Source

Changes in v0.17.6

• chore(deps): update Syft to v1.15.0 (#​505) [anchore-actions-token-generator]
• chore(deps): bump actions/checkout from 4.2.1 to 4.2.2 (#​504) [dependabot]

v0.17.5

Compare Source

Changes in v0.17.5

• chore(deps): update Syft to v1.14.2 (#​503) [anchore-actions-token-generator]

v0.17.4

Compare Source

Changes in v0.17.4

• chore(deps): update Syft to v1.14.1 (#​502) [anchore-actions-token-generator]

v0.17.3

Compare Source

Changes in v0.17.3

• chore(deps): update Syft to v1.14.0 (#​498) [anchore-actions-token-generator]

v0.17.2

Compare Source

Changes in v0.17.2

• Update Syft to v1.11.1 (#​485) [anchore-actions-token-generator]

v0.17.1

Compare Source

Changes in v0.17.1

• chore(deps): update Syft to v1.11.0 (#​483) [anchore-actions-token-generator]

v0.17.0

Compare Source

Changes in v0.17.0

• chore(deps): update Syft to v1.9.0 (#​479) [anchore-actions-token-generator]

v0.16.1

Compare Source

Changes in v0.16.1

• fix: workaround windows install issue (#​477) [willmurphyscode]
• fix: allow users to properly use the file input over the default path value (#​471) [komish]
• chore(deps): update Syft to v1.5.0 (#​470) [anchore-actions-token-generator]
• docs: notes for matrix and required permissions (#​469) [kzantow]
• chore(deps): bump actions/checkout from 4.1.5 to 4.1.6 (#​466) [dependabot]

v0.16.0: v0.16

Compare Source

Changes in v0.16.0

• Update Syft to v1.4.1 (#​465)
• Update GitHub artifact client (#​463) [kzantow]

NOTE: if you are using this action within a matrix build and see failures attempting to upload artifacts with duplicate names, you will need to set the artifact-name to be unique based on the matrix properties (an example here). This is due to a change to use a newer GitHub API which no longer allows artifacts with duplicate names.

v0.15.11

Compare Source

Changes in v0.15.11

• chore(deps): update Syft to v1.3.0 (#​456) [anchore-actions-token-generator]
• chore: remove outdated snapshot workflow (#​457) [spiffcs]
• fix: don't pass in a separate env. This makes it impossible to pass env vars via the action context to syft. (#​455) [iNoahNothing]

v0.15.10

Compare Source

Changes in v0.15.10

• Update Syft to v1.1.0 (#​454)
• Bump Node to v20 on download-syft/publish-sbom actions (#​448) [ViacheslavKudinov]

v0.15.9

Compare Source

Changes in v0.15.9

• reduce syft debug level (#​446) [kzantow]
• update Syft to v0.105.0 (#​442) [anchore-actions-token-generator]

v0.15.8

Compare Source

Changes in v0.15.8

• Update Syft to v0.103.1 (#​441) [anchore-actions-token-generator]

v0.15.7

Compare Source

Changes in v0.15.7

• chore: migrate action to use node v20.11.0 (Iron) FROM node v16.x.x (#​440) [spiffcs]

v0.15.6

Compare Source

Changes in v0.15.6

• chore(deps): update Syft to v0.102.0 (#​438) [anchore-actions-token-generator]

v0.15.5

Compare Source

Changes in v0.15.5

• chore(deps): update Syft to v0.101.1 (#​437) [anchore-actions-token-generator]

v0.15.4

Compare Source

Changes in v0.15.4

• chore(deps): update Syft to v0.101.0 (#​436) [anchore-actions-token-generator]

v0.15.3

Compare Source

Changes in v0.15.3

• chore(deps): update Syft to v0.100.0 (#​435) [anchore-actions-token-generator]

v0.15.2

Compare Source

Changes in v0.15.2

• chore(deps): update Syft to v0.99.0 (#​432) [anchore-actions-token-generator]
• chore: fix github-script invocation in update-snapshots workflow (#​433) [willmurphyscode]

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 4.76%. Comparing base (1dc77ae) to head (8ec3e0d).

Additional details and impacted files

@@             Coverage Diff             @@
##              main      #9       +/-   ##
===========================================
- Coverage   100.00%   4.76%   -95.24%     
===========================================
  Files            1       3        +2     
  Lines            2      42       +40     
===========================================
  Hits             2       2               
- Misses           0      40       +40     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Join our Discord community for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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.