chore(deps): bump the dependencies group with 3 updates

[dependabot]

Bumps the dependencies group with 3 updates: github-community-projects/ospo-reusable-workflows/.github/workflows/auto-labeler.yaml, zizmorcore/zizmor-action and github-community-projects/ospo-reusable-workflows/.github/workflows/release-minimal.yaml.

Updates github-community-projects/ospo-reusable-workflows/.github/workflows/auto-labeler.yaml from 2.2.0 to 2.3.0

Release notes

Sourced from github-community-projects/ospo-reusable-workflows/.github/workflows/auto-labeler.yaml's releases.

v2.3.0

[!NOTE] Optional: release on push instead of pull_request_target. Updating the pinned SHA alone changes nothing. To drop pull_request_target, which the OSPS Baseline scanner flags under OSPS-BR-01.03, change your release workflow's trigger:

on:
  workflow_dispatch:
  push:
    branches: [main]
concurrency:
  group: release
  cancel-in-progress: false

Push runs release only from the default branch. If you switch, don't set filter-by-commitish: true in your release-drafter config. For the auto-labeler, use pull_request and skip fork PRs; see Auto-labeler: Triggering. Full details: Triggering a release.

Changelog

🚀 Features

• feat(release): support releasing on push so callers can drop pull_request_target @​jmeridth (#213)

🧰 Maintenance

• chore(deps): bump the dependencies group with 5 updates @dependabot[bot] (#211)
• chore(deps): bump step-security/harden-runner from 2.21.1 to 2.22.0 in the dependencies group @dependabot[bot] (#210)
• chore(deps): bump anchore/sbom-action/download-syft from 0.24.2 to 0.24.3 in the dependencies group @dependabot[bot] (#209)

See details of all code changes since previous release

Commits

• 3e055d5 feat(release): support releasing on push so callers can drop pull_request_tar...
• 0c69955 chore(deps): bump the dependencies group with 5 updates (#211)
• ab64145 chore(deps): bump step-security/harden-runner (#210)
• 4262f6f chore(deps): bump anchore/sbom-action/download-syft (#209)
• See full diff in compare view

Updates zizmorcore/zizmor-action from 0.6.4 to 0.7.1

Release notes

Sourced from zizmorcore/zizmor-action's releases.

v0.7.1

zizmor changes

Bug Fixes 🐛🔗

• Fixed a regression in 1.31.0 where some ignore comments/configurations would no longer apply to the dangerous-triggers audit

action changes

The default version of zizmor is now 1.31.1.

What's Changed

• Sync zizmor versions by @​github-actions[bot] in zizmorcore/zizmor-action#178

Full Changelog: zizmorcore/zizmor-action@v0.7.0...v0.7.1

v0.7.0

Sponsorship is appreciated!

zizmor notes

Enhancements 🌱🔗

• The typosquat-uses audit now supports pre-commit config inputs (#2437)

• The self-hosted-runner audit is now significantly more precise (#2350)

  Many thanks to @​ubiratansoares for proposing and implementing this enhancement!

• The dangerous-triggers audit now considers the issue_comment trigger fundamentally dangerous (#2396)

• zizmor is now aware of the image_version workflow trigger (#2397)

• The dangerous-triggers audit now produces more precise finding/diagnostic spans (#2402)

• The cache-poisoning audit is now aware of pnpm/setup (#2409)

• The unpinned-images audit now produces more precise findings when the user's workflow contains an indirect matrix (#2395)

  Many thanks to @​ubiratansoares for proposing and implementing this enhancement!

• The cache-poisoning audit is now aware of GitHub's new cache-mode: setting, and will skip any findings that would occur when a job has an effective cache-mode: none (#2418)

• The cache-poisoning audit now flags usages of cache-mode: write and cache-mode: write-only with dangerous triggers, i.e. triggers that give an attacker privileged code execution (#2426)

• zizmor now uses a tree-sitter grammar for PowerShell that's more precise/capable of capturing more non-trivial PowerShell expressions (#2444)

Bug Fixes 🐛🔗

... (truncated)

Commits

• 85b2b9f Sync zizmor versions (#178)
• 38c745a README: bump pins (#177)
• f9597c8 Sync zizmor versions (#175)
• 2181e51 Bump sync-zizmor-versions.py to Python 3.11 for locking (#174)
• 27d989b chore(deps): bump the github-actions group with 2 updates (#173)
• a91218c Bootstrap zizmor without Docker (#169)
• ee3f1bf chore(deps): bump the github-actions group with 2 updates (#170)
• 8eacaa5 README: bump pins (#167)
• See full diff in compare view

Updates github-community-projects/ospo-reusable-workflows/.github/workflows/release-minimal.yaml from 2.2.0 to 2.3.0

Release notes

Sourced from github-community-projects/ospo-reusable-workflows/.github/workflows/release-minimal.yaml's releases.

v2.3.0

[!NOTE] Optional: release on push instead of pull_request_target. Updating the pinned SHA alone changes nothing. To drop pull_request_target, which the OSPS Baseline scanner flags under OSPS-BR-01.03, change your release workflow's trigger:

on:
  workflow_dispatch:
  push:
    branches: [main]
concurrency:
  group: release
  cancel-in-progress: false

Push runs release only from the default branch. If you switch, don't set filter-by-commitish: true in your release-drafter config. For the auto-labeler, use pull_request and skip fork PRs; see Auto-labeler: Triggering. Full details: Triggering a release.

Changelog

🚀 Features

• feat(release): support releasing on push so callers can drop pull_request_target @​jmeridth (#213)

🧰 Maintenance

• chore(deps): bump the dependencies group with 5 updates @dependabot[bot] (#211)
• chore(deps): bump step-security/harden-runner from 2.21.1 to 2.22.0 in the dependencies group @dependabot[bot] (#210)
• chore(deps): bump anchore/sbom-action/download-syft from 0.24.2 to 0.24.3 in the dependencies group @dependabot[bot] (#209)

See details of all code changes since previous release

Commits

• 3e055d5 feat(release): support releasing on push so callers can drop pull_request_tar...
• 0c69955 chore(deps): bump the dependencies group with 5 updates (#211)
• ab64145 chore(deps): bump step-security/harden-runner (#210)
• 4262f6f chore(deps): bump anchore/sbom-action/download-syft (#209)
• 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions