Bump ossf/scorecard-action from 4a0b87a20cc42672e6c80e82e63b5cd8f25f108a to 05bb7c663f6ec9bd8484da0a5b5a77d423e3f88c

[dependabot]

Bumps ossf/scorecard-action from 4a0b87a20cc42672e6c80e82e63b5cd8f25f108a to 05bb7c663f6ec9bd8484da0a5b5a77d423e3f88c.

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

• 05bb7c6 🌱 Bump github.com/docker/cli (#1638)
• 6c4fa3e 🌱 Bump google.golang.org/grpc from 1.76.0 to 1.79.3 (#1639)
• 1979342 🌱 Bump go.opentelemetry.io/otel/sdk from 1.38.0 to 1.40.0 (#1637)
• e465d20 🌱 Bump github.com/go-git/go-git/v5 from 5.16.3 to 5.16.5 (#1635)
• cbc4c36 Log POST failures instead of failing entire action (#1625)
• See full diff 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 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)