Update Scheduled Vulnerability Check and Dependabot configuration

[brfrn169]

Description

This PR updates the Scheduled Vulnerability Check and Dependabot configuration for the ScalarDB 3.17 release.

Related issues and/or PRs

N/A

Changes made

• Updated Scheduled Vulnerability Check and the Dependabot configuration.

Checklist

The following is a best-effort checklist. If any items in this checklist are not applicable to this PR or are dependent on other, unmerged PRs, please still mark the checkboxes after you have read and understood each item.

• I have commented my code, particularly in hard-to-understand areas.
• I have updated the documentation to reflect the changes.
• I have considered whether similar issues could occur in other products, components, or modules if this PR is for bug fixes.
• Any remaining open issues linked to this PR are documented and up-to-date (Jira, GitHub, etc.).
• Tests (unit, integration, etc.) have been added for the changes.
• My changes generate no new warnings.
• Any dependent changes in other PRs have been merged and published.

Additional notes (optional)

N/A

Release notes

N/A

[gemini-code-assist]

Summary of Changes

Hello @brfrn169, 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 ensures that the project's automated dependency and vulnerability scanning mechanisms are correctly configured for the latest ScalarDB 3.17 release cycle. By updating the Dependabot settings, the project maintains its ability to automatically track and update dependencies across its various active branches, contributing to ongoing security and maintenance.

Highlights

• Dependabot Configuration Update: The Dependabot configuration for the github-actions package ecosystem has been updated to align with the ScalarDB 3.17 release. This involves incrementing the target-branch and associated group names across multiple release branches (e.g., from 3.16 to 3.17, 3.15 to 3.16, etc.).

Ignored Files

• Ignored by pattern: .github/workflows/** (2)
  • .github/workflows/remove-untagged-images.yaml
  • .github/workflows/scheduled-vuln-check.yaml

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 Dependabot configuration to target new branches, including the new 3.17 release branch. The changes are straightforward and correct. I've identified a small opportunity to improve maintainability by removing redundant information in the group names for GitHub Actions, which would make future updates less error-prone. I've provided a suggestion for this improvement.

[gemini-code-assist]

The group name actions on branch 3.17 is coupled with the target-branch on line 48. This duplication can lead to inconsistencies in the future if the branch is updated in one place but not the other. To improve maintainability and reduce the chance of error, consider using a more generic group name that doesn't include the branch version. This suggestion applies to all similar github-actions configurations in this file.

      github-actions:

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[Torch3333]

LGTM, thank you!