Fix dependencies

[lexbritvin]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @lexbritvin, 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 comprehensive update of the project's development environment and dependencies. It bumps the Go language version, updates numerous Go modules, and modernizes the golangci-lint configuration. Additionally, the Makefile has been significantly improved to provide a better developer experience with colored output and new convenience targets, alongside minor code adjustments to maintain compatibility with the updated libraries.

Highlights

• Go Version Update: The project's Go language version has been updated from 1.24.0 to 1.25.0, along with the removal of the explicit toolchain directive.
• Dependency Updates: Numerous direct and indirect Go module dependencies have been updated to their latest versions, including github.com/go-git/go-git/v5, github.com/launchrctl/keyring, github.com/launchrctl/launchr, and github.com/pterm/pterm, ensuring the project uses up-to-date libraries.
• GolangCI-Lint Configuration Overhaul: The .golangci.yaml configuration has been significantly refactored to use version: "2" of the config schema. This includes changes to output formats, linter enablement strategy (moving from disable-all: true to default: none), and a more structured approach to exclusions for linters and formatters.
• Makefile Enhancements and Tooling Updates: The Makefile has been modernized with the addition of colored output for better readability, new utility targets like banner, test-short, clean, and help, and an update to golangci-lint to version 2.5.0. A new tool, gotestfmt, has also been integrated for improved test output formatting.
• Codebase Compatibility Fixes: Minor code adjustments were made to ensure compatibility with updated dependencies, specifically adding a type assertion for vaultPass in actionSync.go and updating a go-git API call from file.Blob.Reader() to file.Reader() in actionSync.resources.go.

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 primarily focuses on updating dependencies and improving the developer tooling, including a significant overhaul of the Makefile and the .golangci.yaml configuration. The changes enhance the developer experience with better command-line output and updated linter settings. I've identified a critical issue with an incorrect tool version in the Makefile that will likely cause the build to fail. Additionally, I have a couple of medium-severity suggestions to improve the linter configuration and the consistency of the Makefile.

[lexbritvin]

Waiting a new release on the launchr libs.