chore: bump dependencies to latest versions

[ilopezluna]

bumping some of the deps of #490

[sourcery-ai]

Hey there - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[gemini-code-assist]

Summary of Changes

Hello @ilopezluna, 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 focuses on a routine maintenance task: updating the project's Go module dependencies to their most recent stable versions. This ensures that the codebase benefits from the latest bug fixes, performance improvements, and security patches provided by the upstream libraries, contributing to the overall health and stability of the application. The changes are primarily confined to go.mod, go.sum, and go.work.sum files, reflecting the version bumps.

Highlights

• Dependency Updates: Multiple Go module dependencies have been bumped to their latest versions across cmd/cli, go.mod, go.sum, go.work.sum, and pkg/go-containerregistry.
• Go Standard Library Modules: Dependencies such as golang.org/x/sync, golang.org/x/sys, golang.org/x/term, golang.org/x/crypto, golang.org/x/mod, golang.org/x/net, golang.org/x/text, and golang.org/x/tools have all received minor version updates.
• Third-Party Libraries: Key third-party dependencies like github.com/prometheus/common and golang-jwt/jwt have also been updated, with golang-jwt/jwt specifically moving from v4 to v5 in go.work.sum.
• Checksum Updates: Corresponding go.sum and go.work.sum files have been updated to reflect the new module versions and their respective cryptographic checksums, ensuring integrity and reproducibility.

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 several dependencies across multiple go.mod files to their latest versions. While most of these are minor or patch version bumps, which is good for keeping the project up-to-date with bug fixes and security patches, I've noticed the introduction of github.com/golang-jwt/jwt/v5 in go.work.sum. This is a major version upgrade and could introduce breaking changes. Please ensure this is intentional and that the code has been updated to be compatible with this new version.

[gemini-code-assist]

The introduction of github.com/golang-jwt/jwt/v5 is a major version update from v4. Major version updates often come with breaking API changes. Please verify that all code using this dependency has been updated to work with v5 and that all related tests are passing. It's also worth noting that both v4 and v5 are now present in the workspace dependencies, which could lead to confusion or subtle bugs if not handled carefully.