chore(deps): bump GitHub Actions dependencies

[vnz]

Summary

• Bump actions/checkout from v4 to v6
• Bump extractions/setup-just from v2 to v3

Changes

actions/checkout v4 → v6

• Node.js 24 support
• Credentials now persisted under $RUNNER_TEMP instead of local git config
• Full changelog

extractions/setup-just v2 → v3

• Converted from JavaScript action to composite action
• Full changelog

Test plan

• CI workflow passes with updated actions

🤖 Generated with Claude Code using Dependabot CLI

[gemini-code-assist]

Summary of Changes

Hello @vnz, 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 introduces a new 'dependabot' plugin, enabling users to check for and manage dependency updates across various ecosystems using the Dependabot CLI. It provides a structured workflow for identifying outdated dependencies and offers automated options for creating pull requests to apply these updates, thereby enhancing project maintainability and security.

Highlights

• New Dependabot Plugin Introduced: A new plugin named 'dependabot' has been added, designed to check for dependency updates using the Dependabot CLI.
• Broad Ecosystem Support: The plugin supports a wide array of ecosystems, including GitHub Actions, Terraform, npm, Go, Python, Ruby, Rust, Docker, Maven, Gradle, Composer, NuGet, Helm, Pub (Dart), Swift, and Hex (Elixir).
• Automated Dependency Workflow: It provides a comprehensive workflow covering prerequisite checks, automatic ecosystem detection, running update scans, presenting results, and optionally creating pull requests for identified updates.
• Flexible PR Creation: Users can choose to generate separate pull requests for each ecosystem or a single combined pull request for all detected updates.
• Secure Authentication: The plugin integrates with GitHub CLI for authentication, utilizing 'gh auth token' to securely obtain access tokens.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/ci.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 introduces a new 'dependabot' plugin, including its marketplace entry, configuration, documentation, and a skill definition. The plugin is well-documented and provides a useful capability for checking dependency updates.

My main feedback is regarding a significant discrepancy between the pull request's title/description and its actual content. The title and description refer to bumping GitHub Actions dependencies, while the changes are about adding the new dependabot plugin. This should be corrected to accurately reflect the work done and maintain a clean git history.

Additionally, I've found some correctness issues in the documentation and skill definition regarding the usage of the dependabot-cli command for applying updates, which would lead to incorrect behavior. Please see the detailed comments.

[gemini-code-assist]

The instructions for applying updates are incorrect and will cause the skill to fail. The current command will not modify local files, so the subsequent git commands will have nothing to commit.

1. The description on line 156 ("Run dependabot update without --local") is misleading. The key difference between dry-run and apply mode for local files is omitting the trailing . from the command, not the --local flag itself.
2. The command on line 159 is missing the --local flag. It will operate on a fresh clone from GitHub, not the local working directory.
3. The note on line 161 is incorrect; non-local mode does not modify local files in place.

To fix this, the command must use the --local flag, and the surrounding text should be updated for clarity and correctness.

Suggested change

	2. **Run dependabot update without --local** to apply changes:
	```bash
	REPO=$(gh repo view --json owner,name --jq '.owner.login + "/" + .name')
	LOCAL_GITHUB_ACCESS_TOKEN=$(gh auth token) dependabot update <ecosystem> "$REPO"
	```
	Note: The non-local mode modifies files in place.
	2. **Run dependabot update in apply mode** to apply changes:
	```bash
	REPO=$(gh repo view --json owner,name --jq '.owner.login + "/" + .name')
	LOCAL_GITHUB_ACCESS_TOKEN=$(gh auth token) dependabot update <ecosystem> "$REPO" --local

Note: The --local flag without a trailing directory path modifies files in place.

[gemini-code-assist]

The command for applying updates to a local checkout is incorrect. The dependabot update command is missing the --local flag. Without it, dependabot-cli will clone the repository from GitHub instead of using the local files, which contradicts the section's goal of running locally. The command should include --local to modify the files in the current directory.

Suggested change

	LOCAL_GITHUB_ACCESS_TOKEN=$(gh auth token) dependabot update <ecosystem> <owner/repo>
	LOCAL_GITHUB_ACCESS_TOKEN=$(gh auth token) dependabot update <ecosystem> <owner/repo> --local