• Icon: Task Task
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • GRC
    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • GRC Sprint 2025-06
    • No

      Upgrade these packages in the Makefile:

      • github.com/golangci/golangci-lint/cmd/golangci-lint@v1.55.1
      • github.com/daixiang0/gci@v0.11.2
      • sigs.k8s.io/kustomize/kustomize/v5@v5.2.1
      • github.com/securego/gosec/v2/cmd/gosec@v2.18.2
         
        The linter upgrade often requires manual steps to account for recommended formatting or logic, and v1.55 is no exception.

      The one linter I'm not sure is necessary that I've found so far is this rule, since we intentionally check error messages, so using require (which would halt the test on failure) I don't think is desired behavior:

      issues: 
         exclude: 
           - "require-error: for error assertions use require"
      

      A sample PR has been opened:

              yikim@redhat.com Yi Rae Kim
              rh-ee-dhaiduce Dale Haiducek
              Derek Ho Derek Ho
              ACM GRC & Gatekeeper
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: