Originally created by: dependabot[bot]
Bumps ossf/scorecard-action from [55891b] to 2d1146689b8cda280b9bc96326124645441f03bc.
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
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 (github.com) 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)
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.
Originally posted by: dependabot[bot]
Labels
The following labels could not be found:
automated,dependencies. Please create them before Dependabot can add them to a pull request.Please fix the above issues or remove invalid values from
dependabot.yml.