ci: Enhance GitHub Actions security with zizmor --fix=all

[Pr0methean]

Fixes #531

[gemini-code-assist]

Summary of Changes

Hello @Pr0methean, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the repository's security and stability by implementing a 7-day cooldown period for Dependabot updates across all configured package ecosystems. This change aims to provide a more controlled and predictable dependency update process, reducing the frequency of automated PRs and allowing more time for review and integration of new versions.

Highlights

• Dependabot Configuration: A cooldown period of 7 days has been added to all Dependabot configurations in .github/dependabot.yml. This applies to the cargo package ecosystems (root, fuzz, fuzz/read, fuzz/write) and the github-actions ecosystem.

Ignored Files

• Ignored by pattern: .github/workflows/** (5)
  • .github/workflows/auto_merge_prs.yml
  • .github/workflows/ci.yaml
  • .github/workflows/codeql.yml
  • .github/workflows/devskim.yml
  • .github/workflows/release-plz.yml

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request enhances security by adding a 7-day cooldown period for Dependabot across all configured package ecosystems. This prevents Dependabot from immediately reopening closed pull requests, which is a good practice. The changes are applied consistently and correctly in dependabot.yml.

[amazon-q-developer]

Security Enhancement Review

This PR implements security improvements suggested by zizmor --fix=all to enhance GitHub Actions security. The changes include:

✅ Good Security Practices:

• Adding persist-credentials: false to all checkout actions prevents credential leakage
• Adding Dependabot cooldown periods reduces PR spam
• Using pinned action versions with SHA hashes

⚠️ Critical Issues Found:

• Auto-merge workflow logic error: The mixed use of github.actor and github.event.pull_request.user.login creates inconsistent behavior that could break legitimate GitHub Actions auto-merges
• Inconsistent conditional logic: The job condition and step conditions use different actor checking methods

Recommendation: Fix the actor checking logic in the auto-merge workflow before merging. The security improvements are valuable, but the workflow logic needs to be consistent to prevent breaking legitimate automation.

The PR title correctly follows Conventional Commits format with the ci: prefix as required by the project guidelines.

---

You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.