Bump ossf/scorecard-action from 620fd28d6b2ba01c1d70cf63dfb4bdf868e19d6f to 57ac50d56545907aaa63be8a91227b7535966fd3

[dependabot]

Bumps ossf/scorecard-action from 620fd28d6b2ba01c1d70cf63dfb4bdf868e19d6f to 57ac50d56545907aaa63be8a91227b7535966fd3.

Changelog

Sourced from ossf/scorecard-action's changelog.

Releasing the scorecard GitHub Action

This is a draft document to describe the release process for the scorecard GitHub Action.

(If there are improvements you'd like to see, please comment on the tracking issue or issue a pull request to discuss.)

• Tracking
• Preparing the release
  • Validate the Action
  • Update the scorecard version
• Drafting release notes
• Release
  • Create a tag
  • Create a GitHub release
• Update the starter workflow
• Announce

Tracking

As the first task, a Release Manager should open a tracking issue for the release.

We don't currently have a template for releasing, but the following issue is a good example to draw inspiration from.

We're not striving for perfection with the template, but the tracking issue will serve as a reference point to aggregate feedback, so try your best to be as descriptive as possible.

Preparing the release

This section covers changes that need to be issued as a pull request and should be merged before releasing the scorecard GitHub Action.

Validate the Action

Manually run the workflow scorecards.yml and verify that the run succeeds.

Update the scorecard-action version

NOTE: we have a chicken-and-egg problem where the commit to be used for the release needs to have the image tag that only gets created after the commit is pushed. We workaround that by pre-selecting and referencing the image tag instead of the SHA which isn't ideal but workable.

... (truncated)

Commits

• 57ac50d 🌱 Bump github.com/go-viper/mapstructure/v2 from 2.3.0 to 2.4.0 (#1573)
• 7a0b15a docs: clarify GITHUB_TOKEN permissions needed for private repos (#1574)
• 9db932c setup codeowners for requesting reviews (#1576)
• f35c645 add missing top-level token permissions to workflows (#1566)
• f815119 🌱 Bump golang.org/x/net from 0.41.0 to 0.42.0 (#1563)
• d6e7935 🌱 Bump golang in the docker-images group (#1562)
• 40f93ad 🌱 Bump the github-actions group with 2 updates (#1560)
• 4108ecd 🌱 Bump github.com/go-viper/mapstructure/v2 from 2.2.1 to 2.3.0 (#1559)
• 52f7f99 Update README.md (#1561)
• 0993460 🌱 Bump github.com/sigstore/cosign/v2 from 2.5.0 to 2.5.2 (#1558)
• 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)