send
send copied to clipboard
build(deps): bump ossf/scorecard-action from 2.3.1 to 2.4.2
Bumps ossf/scorecard-action from 2.3.1 to 2.4.2.
Release notes
Sourced from ossf/scorecard-action's releases.
v2.4.2
What's Changed
This update bumps the Scorecard version to the v5.2.1 release. For a complete list of changes, please refer to the Scorecard v5.2.0 and v5.2.1 release notes.
Full Changelog: https://github.com/ossf/scorecard-action/compare/v2.4.1...v2.4.2
v2.4.1
What's Changed
- This update bumps the Scorecard version to the v5.1.1 release. For a complete list of changes, please refer to the v5.1.0 and v5.1.1 release notes.
- Publishing results now uses half the API quota as before. The exact savings depends on the repository in question.
- use Scorecard library entrypoint instead of Cobra hooking by
@spencerschrockin ossf/scorecard-action#1423- Some errors were made into annotations to make them more visible
- Make default branch error more prominent by
@jsorefin ossf/scorecard-action#1459- There is now an optional
file_modeinput which controls how repository files are fetched from GitHub. The default isarchive, butgitproduces the most accurate results for repositories with.gitattributesfiles at the cost of analysis speed.
- add input for specifying
--file-modeby@spencerschrockin ossf/scorecard-action#1509- The underlying container for the action is now hosted on GitHub Container Registry. There should be no functional changes.
- :seedling: publish docker images to GitHub Container Registry by
@spencerschrockin ossf/scorecard-action#1453Docs
- Installation docs update by
@JeremiahAHowardin ossf/scorecard-action#1416New Contributors
@JeremiahAHowardmade their first contribution in ossf/scorecard-action#1416@jsorefmade their first contribution in ossf/scorecard-action#1459 Full Changelog: https://github.com/ossf/scorecard-action/compare/v2.4.0...v2.4.1v2.4.0
What's Changed
This update bumps the Scorecard version to the v5 release. For a complete list of changes, please refer to the v5.0.0 release notes. Of special note to Scorecard Action is the Maintainer Annotation feature, which can be used to suppress some Code Scanning false positives. Alerts will not be generated for any Scorecard Check with an annotation.
- :seedling: Bump github.com/ossf/scorecard/v5 from v5.0.0-rc2 to v5.0.0 by
@spencerschrockin ossf/scorecard-action#1410- :bug: lower license sarif alert threshold to 9 by
@spencerschrockin ossf/scorecard-action#1411Documentation
- docs: dogfooding badge by
@jkowalleckin ossf/scorecard-action#1399New Contributors
@jkowalleckmade their first contribution in ossf/scorecard-action#1399Full Changelog: https://github.com/ossf/scorecard-action/compare/v2.3.3...v2.4.0
v2.3.3
[!NOTE]
There is no v2.3.2 release as a step was skipped in the release process. This was fixed and re-released under the v2.3.3 tagWhat's Changed
- :seedling: Bump github.com/ossf/scorecard/v4 (v4.13.1) to github.com/ossf/scorecard/v5 (v5.0.0-rc1) by
@spencerschrockin ossf/scorecard-action#1366- :seedling: Bump github.com/ossf/scorecard/v5 from v5.0.0-rc1 to v5.0.0-rc2 by
@spencerschrockin ossf/scorecard-action#1374
... (truncated)
Commits
05b42c6:seedling: bump docker to ghcr v2.4.2 (#1548)b225da6Bump github.com/ossf/scorecard/v5 from v5.2.0 to v5.2.1 (#1550)9399f6f:seedling: Bump the docker-images group across 1 directory with 2 updates (#1...e1daa8c:seedling: Bump the github-actions group across 1 directory with 5 updates (#...9fe6511:seedling: Bump golang.org/x/net from 0.39.0 to 0.40.0 (#1542)25b9cd9:seedling: Bump github.com/ossf/scorecard/v5 from v5.1.1 to v5.2.0 (#1547)18cc9b8:seedling: Bump golang.org/x/net from 0.38.0 to 0.39.0 (#1536)db78142:seedling: Bump the github-actions group with 2 updates (#1538)de386ed:seedling: Bump golang from 1.24.1 to 1.24.2 in the docker-images group (#1534)5b7cedb:seedling: Bump github.com/sigstore/cosign/v2 from 2.4.3 to 2.5.0 (#1537)- 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)