Skip to content

chore: update the trunk conf file #2217

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

matthewmcneely
Copy link
Member

Description

This PR updates the trunk config to use the current support go toolchain version and upgrades used linters.

Checklist

  • Code compiles correctly and linting passes locally

@Copilot Copilot AI review requested due to automatic review settings August 4, 2025 17:22
@matthewmcneely matthewmcneely requested a review from a team as a code owner August 4, 2025 17:22
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR updates the trunk configuration file to use newer versions of the Go toolchain and various linters. The update includes upgrading the trunk CLI version, plugin reference, Go runtime, and multiple linting tools to their latest supported versions.

  • Updates trunk CLI from 1.22.10 to 1.24.0 and plugins from v1.6.7 to v1.7.1
  • Upgrades Go runtime from 1.23.5 to 1.24.5
  • Updates multiple linters including trivy, renovate, checkov, golangci-lint, and others to newer versions
Comments suppressed due to low confidence (1)

.trunk/trunk.yaml:29

  • The package '[email protected]' appears to be incorrect. This should likely be '[email protected]' or the version number may be wrong for golangci-lint2 if it's a different package.

@matthewmcneely matthewmcneely enabled auto-merge (squash) August 4, 2025 23:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant