Update to v2.2.4

[another-rex]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @another-rex, 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 updates the version of the OSV-Scanner action to v2.2.4 across its documentation and action configurations. The primary goal is to ensure that all components and references are aligned with the latest release, providing users with the most current and stable version of the tool.

Highlights

• Version Update: All references to the OSV-Scanner action have been updated to version v2.2.4.
• Documentation Consistency: The README.md badge now correctly displays the v2.2.4 release version.
• Action Configuration: The Docker image tags in both osv-reporter-action/action.yml and osv-scanner-action/action.yml have been updated to v2.2.4.

Ignored Files

• Ignored by pattern: .github/workflows/** (3)
  • .github/workflows/osv-scanner-reusable-pr.yml
  • .github/workflows/osv-scanner-reusable.yml
  • .github/workflows/osv-scanner-unified-workflow.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 updates the action version to v2.2.4 across the README and action configuration files. The changes are correct for a version bump. My review includes suggestions to improve maintainability by automating parts of the release process, such as using a dynamic version badge and centralizing the version number to avoid manual updates in multiple files.

[gemini-code-assist]

To avoid manually updating the version in the README for each release, you can use a dynamic badge from shields.io that automatically displays the latest GitHub release version. This would ensure the badge is always up-to-date without any manual intervention.

Suggested change

	[](https://github.com/google/osv-scanner-action/releases)
	[](https://github.com/google/osv-scanner-action/releases)

[gemini-code-assist]

The version string v2.2.4 is hardcoded here and in other files (osv-scanner-action/action.yml, README.md). Manually updating the version in multiple places is error-prone and can lead to inconsistencies if a location is missed. To improve maintainability, consider automating this process. A release script could read the version from a single source of truth (e.g., a version file or git tag) and use a tool to update all occurrences. This would make future releases more robust and less dependent on manual changes.