8000 chore(ci): update golangci-lint GitHub Action to v8 by reject-i · Pull Request #91 · kkrt-labs/go-utils · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

chore(ci): update golangci-lint GitHub Action to v8 #91

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

reject-i
Copy link
@reject-i reject-i commented Jun 2, 2025

📝 Description

Updates golangci/golangci-lint-action from v6 to v8 in .github/workflows/test.yml to ensure compatibility with the latest GitHub Actions features and improved performance.

The current linter version is v1.64.7, which is fully supported by the v8 action release.
Reference: https://github.com/golangci/golangci-lint-action/releases/tag/v8.0.0

🔄 Change

  • ✨ New feature (e.g. API route, major perf improvement...)
  • 🐛 Bug fix
  • 🧹 Chore (e.g. package upgrades, configuration change, refactor, small perf improvement, typos...)
  • 🧪 Tests
  • 🏭 DevOps (e.g. CI-CD, development environment upgrade, security upgrade, automation addition...)
  • 📚 Documentation

📋 Checklist

  • I have added tests to cover my changes, if applicable.
  • I have updated relevant documentation for my changes.
  • I have included references to issues resolved by this Pull Request
  • I have set a Pull Request title that respects gitmoji
  • I have set a Pull Request's label to one of type.feat,type.fix,type.chore,type.test,type.docs,type.devops
  • I have set a Pull Request's label to one of breaking-change or non-breaking-change
  • I have documented breaking changes and migration path, if applicable

@reject-i reject-i requested a review from nmvalera as a code owner June 2, 2025 10:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant
0