Bump zizmor from 1.0.0 to 1.3.0

[dependabot]

Bumps zizmor from 1.0.0 to 1.3.0.

Release notes

Sourced from zizmor's releases.

v1.3.0

This release comes with one new audit (overprovisioned-secrets), plus a handful of bugfixes and analysis improvements to existing audits. It also comes with a special easter egg for those who wish to kvell about their audit results.

New Features 🌈🔗

• New audit: overprovisioned-secrets detects uses of the secrets context that result in excessive secret provisioning (#485)
• Added a special naches mode for when you're feeling particularly proud of your audit results (#490)

Improvements 🌱🔗

• zizmor produces slightly more informative error messages when given an invalid input file (#482)
• Case insensitivity in contexts is now handeled more consistently and pervasively (#491)

Bug Fixes 🐛🔗

• Fixed a bug where zizmor would fail to discover actions within subdirectories of .github/workflows (#477)
• Fixed a bug where zizmor would fail to parse composite action definitions with no name field (#487)

v1.2.2

Bug Fixes 🐛🔗

• The excessive-permissions audit is now more precise about both reusable workflows and reusable workflow calls (#473)

Improvements 🌱🔗

• Fetch failures when running zizmor org/repo are now more informative (#475)

v1.2.1

This is a small corrective release for some SARIF behavior that changed with v1.2.0.

Bug Fixes 🐛🔗

• SARIF outputs now use relative paths again, but more correctly than before v1.2.0 (#469)

v1.2.0

This release comes with one new audit (bot-conditions), plus a handful of bugfixes and analysis improvements to existing audits.

One bugfix in this release is also a slight behavior change: zizmor now emits SARIF outputs with absolute paths. This should not affect most users, but may make it slightly harder to share SARIF outputs between machines without fully reproducing exact file paths. If this affects you, please let us know!

New Features 🌈🔗

• New audit: bot-conditions detects spoofable uses of github.actor within dangerous triggers (#460)

Improvements 🌱🔗

• The unpinned-uses audit no longer flags local reusable workflows or actions as unpinned/unhashed (#439)
• The excessive-permissions audit has been refactored, and better captures both true positive and true negative cases (#441)
• The SARIF output mode (--format=sarif) now always returns absolute paths in its location information, rather than attempting to infer a (sometimes incorrect) repository-relative path (#453)
• zizmor now provides manylinux wheel builds for aarch64 (#457)

... (truncated)

Changelog

Sourced from zizmor's changelog.

v1.3.0

This release comes with one new audit ([overprovisioned-secrets]), plus a handful of bugfixes and analysis improvements to existing audits. It also comes with a special easter egg for those who wish to kvell about their audit results.

New Features 🌈

• New audit: [overprovisioned-secrets] detects uses of the secrets context that result in excessive secret provisioning (#485)
• Added a special naches mode for when you're feeling particularly proud of your audit results (#490)

Improvements 🌱

• zizmor produces slightly more informative error messages when given an invalid input file (#482)
• Case insensitivity in contexts is now handeled more consistently and pervasively (#491)

Bug Fixes 🐛

• Fixed a bug where zizmor would fail to discover actions within subdirectories of .github/workflows (#477)
• Fixed a bug where zizmor would fail to parse composite action definitions with no name field (#487)

v1.2.2

Bug Fixes 🐛

• The [excessive-permissions] audit is now more precise about both reusable workflows and reusable workflow calls (#473)

Improvements 🌱

• Fetch failures when running zizmor org/repo are now more informative (#475)

v1.2.1

This is a small corrective release for some SARIF behavior that changed with v1.2.0.

Bug Fixes 🐛

• SARIF outputs now use relative paths again, but more correctly than before v1.2.0 (#469)

v1.2.0

... (truncated)

Commits

• e61a9d7 chore: prep for 1.3.0 release (#500)
• 3995d99 docs: bump trophies (#499)
• 84c9524 deps: bump indicatif from 0.17.9 to 0.17.11 (#498)
• 1719760 Downgrade tracing-indicatif (#496)
• 1cfe268 docs: bump trophies (#495)
• ac712da ci: attempt to fix arm build (#494)
• eef67b2 chore(deps): bump the github-actions group with 3 updates (#493)
• 0925c31 chore(deps): bump the cargo group with 2 updates (#492)
• 4fdfdb6 refactor: improve context handling (#491)
• eb31888 feat(cli): add naches mode (#490)
• 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)