Skip to content

Migrate golangci-lint config to v2 and bump linter to v2.13.2 - #1761

Merged
ljkiraly merged 1 commit into
mainfrom
pilot-golangci-v2
Sep 2, 2026
Merged

Migrate golangci-lint config to v2 and bump linter to v2.13.2#1761
ljkiraly merged 1 commit into
mainfrom
pilot-golangci-v2

Conversation

@ljkiraly

@ljkiraly ljkiraly commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

Description

golangci-lint v1.64.2 (built with go1.24) fails on this repository under Go 1.25: it errors on the "go 1.25" config target and exhibits pathological memory use (>16GB, never completing) that causes the CI runner to be killed. A release built with go1.25+ resolves both problems (completes in ~40s at ~1.5GB).

  • Migrate .golangci.yml from the v1 to the v2 format and set run.go to "1.25".
  • Bump linter-version in ci.yaml from v1.64.2 to v2.13.2 (built with go1.27) so CI runs the v2 linter against the v2 config atomically.
  • Suppress noise introduced by v2's newer/stricter analyzers so the effective policy matches v1 behavior:
    • goconst: min-occurrences 2 -> 3; exclude test and testutil helpers
    • gosec: exclude G304/G702/G703 (file-inclusion and taint-analysis rules on process-controlled paths, not external input)
    • staticcheck: disable SA4023 (interface nil-comparison false positive) and QF1001/QF1003/QF1008/QF1012 (quickfix style suggestions)
    • govet: disable the new go1.27 "inline" analyzer

Result: golangci-lint run reports 0 issues.

How Has This Been Tested?

  • Added unit testing to cover
  • Tested manually
  • Tested by integration testing
  • Have not tested

Types of changes

  • Bug fix
  • New functionality
  • Documentation
  • Refactoring
  • CI

@ljkiraly
Migrate golangci-lint config to v2 and bump linter to v2.13.2
aa103db 
golangci-lint v1.64.2 (built with go1.24) fails on this repository under
Go 1.25: it errors on the "go 1.25" config target and exhibits pathological
memory use (>16GB, never completing) that causes the CI runner to be killed.
A release built with go1.25+ resolves both problems (completes in ~40s at
~1.5GB).

- Migrate .golangci.yml from the v1 to the v2 format and set run.go to "1.25".
- Bump linter-version in ci.yaml from v1.64.2 to v2.13.2 (built with go1.27)
  so CI runs the v2 linter against the v2 config atomically.
- Suppress noise introduced by v2's newer/stricter analyzers so the effective
  policy matches v1 behavior:
    * goconst: min-occurrences 2 -> 3; exclude test and testutil helpers
    * gosec: exclude G304/G702/G703 (file-inclusion and taint-analysis rules
      on process-controlled paths, not external input)
    * staticcheck: disable SA4023 (interface nil-comparison false positive)
      and QF1001/QF1003/QF1008/QF1012 (quickfix style suggestions)
    * govet: disable the new go1.27 "inline" analyzer

Result: golangci-lint run reports 0 issues.
Assisted-by: Kiro (AI assistant)

Signed-off-by: Laszlo Kiraly <laszlo.kiraly@est.tech>
@ljkiraly
ljkiraly requested review from szvincze and zolug September 1, 2026 15:13
szvincze
szvincze approved these changes Sep 1, 2026
View reviewed changes

@szvincze szvincze left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM

@ljkiraly
ljkiraly merged commit 8c8366a into main Sep 2, 2026
23 of 25 checks passed
@ljkiraly
ljkiraly deleted the pilot-golangci-v2 branch September 2, 2026 13:32
This was referenced Sep 2, 2026
Merged
Merged
Merged
Merged
Merged
Merged
Merged
Merged
Merged
Merged
Merged
Merged
Merged
nsmbot added a commit to networkservicemesh/cmd-dashboard-backend that referenced this pull request Sep 2, 2026
@nsmbot NSMBot
Update go.mod and go.sum to latest version from networkservicemesh/sd…
8b972c2 
…k@main (#107)

PR link: networkservicemesh/sdk#1761

Commit: 8c8366a
Author: Laszlo Kiraly
Date: 2026-09-02 15:32:01 +0200
Message:
  - Migrate golangci-lint config to v2 and bump linter to v2.13.2 (#1761)
golangci-lint v1.64.2 (built with go1.24) fails on this repository under
Go 1.25: it errors on the "go 1.25" config target and exhibits pathological
memory use (>16GB, never completing) that causes the CI runner to be killed.
A release built with go1.25+ resolves both problems (completes in ~40s at
~1.5GB).
- Migrate .golangci.yml from the v1 to the v2 format and set run.go to "1.25".
- Bump linter-version in ci.yaml from v1.64.2 to v2.13.2 (built with go1.27)
  so CI runs the v2 linter against the v2 config atomically.
- Suppress noise introduced by v2's newer/stricter analyzers so the effective
  policy matches v1 behavior:
    * goconst: min-occurrences 2 -> 3; exclude test and testutil helpers
    * gosec: exclude G304/G702/G703 (file-inclusion and taint-analysis rules
      on process-controlled paths, not external input)
    * staticcheck: disable SA4023 (interface nil-comparison false positive)
      and QF1001/QF1003/QF1008/QF1012 (quickfix style suggestions)
    * govet: disable the new go1.27 "inline" analyzer
Result: golangci-lint run reports 0 issues.
Assisted-by: Kiro (AI assistant)

Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
Co-authored-by: NSMBot <nsmbot@networkservicmesh.io>
nsmbot added a commit to networkservicemesh/cmd-registry-proxy-dns that referenced this pull request Sep 2, 2026
@nsmbot NSMBot
Update go.mod and go.sum to latest version from networkservicemesh/sd…
01204b4 
…k@main (#722)

PR link: networkservicemesh/sdk#1761

Commit: 8c8366a
Author: Laszlo Kiraly
Date: 2026-09-02 15:32:01 +0200
Message:
  - Migrate golangci-lint config to v2 and bump linter to v2.13.2 (#1761)
golangci-lint v1.64.2 (built with go1.24) fails on this repository under
Go 1.25: it errors on the "go 1.25" config target and exhibits pathological
memory use (>16GB, never completing) that causes the CI runner to be killed.
A release built with go1.25+ resolves both problems (completes in ~40s at
~1.5GB).
- Migrate .golangci.yml from the v1 to the v2 format and set run.go to "1.25".
- Bump linter-version in ci.yaml from v1.64.2 to v2.13.2 (built with go1.27)
  so CI runs the v2 linter against the v2 config atomically.
- Suppress noise introduced by v2's newer/stricter analyzers so the effective
  policy matches v1 behavior:
    * goconst: min-occurrences 2 -> 3; exclude test and testutil helpers
    * gosec: exclude G304/G702/G703 (file-inclusion and taint-analysis rules
      on process-controlled paths, not external input)
    * staticcheck: disable SA4023 (interface nil-comparison false positive)
      and QF1001/QF1003/QF1008/QF1012 (quickfix style suggestions)
    * govet: disable the new go1.27 "inline" analyzer
Result: golangci-lint run reports 0 issues.
Assisted-by: Kiro (AI assistant)

Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
Co-authored-by: NSMBot <nsmbot@networkservicmesh.io>
nsmbot added a commit to networkservicemesh/sdk-kernel that referenced this pull request Sep 2, 2026
@nsmbot NSMBot
Update go.mod and go.sum to latest version from networkservicemesh/sd…
0f93066 
…k@main (#748)

PR link: networkservicemesh/sdk#1761

Commit: 8c8366a
Author: Laszlo Kiraly
Date: 2026-09-02 15:32:01 +0200
Message:
  - Migrate golangci-lint config to v2 and bump linter to v2.13.2 (#1761)
golangci-lint v1.64.2 (built with go1.24) fails on this repository under
Go 1.25: it errors on the "go 1.25" config target and exhibits pathological
memory use (>16GB, never completing) that causes the CI runner to be killed.
A release built with go1.25+ resolves both problems (completes in ~40s at
~1.5GB).
- Migrate .golangci.yml from the v1 to the v2 format and set run.go to "1.25".
- Bump linter-version in ci.yaml from v1.64.2 to v2.13.2 (built with go1.27)
  so CI runs the v2 linter against the v2 config atomically.
- Suppress noise introduced by v2's newer/stricter analyzers so the effective
  policy matches v1 behavior:
    * goconst: min-occurrences 2 -> 3; exclude test and testutil helpers
    * gosec: exclude G304/G702/G703 (file-inclusion and taint-analysis rules
      on process-controlled paths, not external input)
    * staticcheck: disable SA4023 (interface nil-comparison false positive)
      and QF1001/QF1003/QF1008/QF1012 (quickfix style suggestions)
    * govet: disable the new go1.27 "inline" analyzer
Result: golangci-lint run reports 0 issues.
Assisted-by: Kiro (AI assistant)

Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
Co-authored-by: NSMBot <nsmbot@networkservicmesh.io>
nsmbot pushed a commit to networkservicemesh/deployments-k8s that referenced this pull request Sep 2, 2026
NSMBot
Update go.mod and go.sum to latest version from networkservicemesh/cm…
c1301ba 
…d-dashboard-backend@main

PR link: networkservicemesh/cmd-dashboard-backend#107

Commit: 8b972c2
Author: Network Service Mesh Bot
Date: 2026-09-02 08:44:08 -0500
Message:
  - Update go.mod and go.sum to latest version from networkservicemesh/sdk@main (#107)
PR link: networkservicemesh/sdk#1761
Commit: 8c8366a
Author: Laszlo Kiraly
Date: 2026-09-02 15:32:01 +0200
Message:
    - Migrate golangci-lint config to v2 and bump linter to v2.13.2 (#1761)
golangci-lint v1.64.2 (built with go1.24) fails on this repository under
Go 1.25: it errors on the "go 1.25" config target and exhibits pathological
memory use (>16GB, never completing) that causes the CI runner to be killed.
A release built with go1.25+ resolves both problems (completes in ~40s at
~1.5GB).
- Migrate .golangci.yml from the v1 to the v2 format and set run.go to "1.25".
- Bump linter-version in ci.yaml from v1.64.2 to v2.13.2 (built with go1.27)
  so CI runs the v2 linter against the v2 config atomically.
- Suppress noise introduced by v2's newer/stricter analyzers so the effective
  policy matches v1 behavior:
    * goconst: min-occurrences 2 -> 3; exclude test and testutil helpers
    * gosec: exclude G304/G702/G703 (file-inclusion and taint-analysis rules
      on process-controlled paths, not external input)
    * staticcheck: disable SA4023 (interface nil-comparison false positive)
      and QF1001/QF1003/QF1008/QF1012 (quickfix style suggestions)
    * govet: disable the new go1.27 "inline" analyzer
Result: golangci-lint run reports 0 issues.
Assisted-by: Kiro (AI assistant)
Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
nsmbot added a commit to networkservicemesh/cmd-csi-driver that referenced this pull request Sep 2, 2026
@nsmbot NSMBot
Update go.mod and go.sum to latest version from networkservicemesh/sd…
bd2e1df 
…k@main (#139)

PR link: networkservicemesh/sdk#1761

Commit: 8c8366a
Author: Laszlo Kiraly
Date: 2026-09-02 15:32:01 +0200
Message:
  - Migrate golangci-lint config to v2 and bump linter to v2.13.2 (#1761)
golangci-lint v1.64.2 (built with go1.24) fails on this repository under
Go 1.25: it errors on the "go 1.25" config target and exhibits pathological
memory use (>16GB, never completing) that causes the CI runner to be killed.
A release built with go1.25+ resolves both problems (completes in ~40s at
~1.5GB).
- Migrate .golangci.yml from the v1 to the v2 format and set run.go to "1.25".
- Bump linter-version in ci.yaml from v1.64.2 to v2.13.2 (built with go1.27)
  so CI runs the v2 linter against the v2 config atomically.
- Suppress noise introduced by v2's newer/stricter analyzers so the effective
  policy matches v1 behavior:
    * goconst: min-occurrences 2 -> 3; exclude test and testutil helpers
    * gosec: exclude G304/G702/G703 (file-inclusion and taint-analysis rules
      on process-controlled paths, not external input)
    * staticcheck: disable SA4023 (interface nil-comparison false positive)
      and QF1001/QF1003/QF1008/QF1012 (quickfix style suggestions)
    * govet: disable the new go1.27 "inline" analyzer
Result: golangci-lint run reports 0 issues.
Assisted-by: Kiro (AI assistant)

Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
Co-authored-by: NSMBot <nsmbot@networkservicmesh.io>
nsmbot added a commit to networkservicemesh/cmd-map-ip-k8s that referenced this pull request Sep 2, 2026
@nsmbot NSMBot
Update go.mod and go.sum to latest version from networkservicemesh/sd…
30ef786 
…k@main (#297)

PR link: networkservicemesh/sdk#1761

Commit: 8c8366a
Author: Laszlo Kiraly
Date: 2026-09-02 15:32:01 +0200
Message:
  - Migrate golangci-lint config to v2 and bump linter to v2.13.2 (#1761)
golangci-lint v1.64.2 (built with go1.24) fails on this repository under
Go 1.25: it errors on the "go 1.25" config target and exhibits pathological
memory use (>16GB, never completing) that causes the CI runner to be killed.
A release built with go1.25+ resolves both problems (completes in ~40s at
~1.5GB).
- Migrate .golangci.yml from the v1 to the v2 format and set run.go to "1.25".
- Bump linter-version in ci.yaml from v1.64.2 to v2.13.2 (built with go1.27)
  so CI runs the v2 linter against the v2 config atomically.
- Suppress noise introduced by v2's newer/stricter analyzers so the effective
  policy matches v1 behavior:
    * goconst: min-occurrences 2 -> 3; exclude test and testutil helpers
    * gosec: exclude G304/G702/G703 (file-inclusion and taint-analysis rules
      on process-controlled paths, not external input)
    * staticcheck: disable SA4023 (interface nil-comparison false positive)
      and QF1001/QF1003/QF1008/QF1012 (quickfix style suggestions)
    * govet: disable the new go1.27 "inline" analyzer
Result: golangci-lint run reports 0 issues.
Assisted-by: Kiro (AI assistant)

Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
Co-authored-by: NSMBot <nsmbot@networkservicmesh.io>
nsmbot pushed a commit to networkservicemesh/deployments-k8s that referenced this pull request Sep 2, 2026
NSMBot
Update go.mod and go.sum to latest version from networkservicemesh/cm…
f03074c 
…d-registry-proxy-dns@main

PR link: networkservicemesh/cmd-registry-proxy-dns#722

Commit: 01204b4
Author: Network Service Mesh Bot
Date: 2026-09-02 08:44:16 -0500
Message:
  - Update go.mod and go.sum to latest version from networkservicemesh/sdk@main (#722)
PR link: networkservicemesh/sdk#1761
Commit: 8c8366a
Author: Laszlo Kiraly
Date: 2026-09-02 15:32:01 +0200
Message:
    - Migrate golangci-lint config to v2 and bump linter to v2.13.2 (#1761)
golangci-lint v1.64.2 (built with go1.24) fails on this repository under
Go 1.25: it errors on the "go 1.25" config target and exhibits pathological
memory use (>16GB, never completing) that causes the CI runner to be killed.
A release built with go1.25+ resolves both problems (completes in ~40s at
~1.5GB).
- Migrate .golangci.yml from the v1 to the v2 format and set run.go to "1.25".
- Bump linter-version in ci.yaml from v1.64.2 to v2.13.2 (built with go1.27)
  so CI runs the v2 linter against the v2 config atomically.
- Suppress noise introduced by v2's newer/stricter analyzers so the effective
  policy matches v1 behavior:
    * goconst: min-occurrences 2 -> 3; exclude test and testutil helpers
    * gosec: exclude G304/G702/G703 (file-inclusion and taint-analysis rules
      on process-controlled paths, not external input)
    * staticcheck: disable SA4023 (interface nil-comparison false positive)
      and QF1001/QF1003/QF1008/QF1012 (quickfix style suggestions)
    * govet: disable the new go1.27 "inline" analyzer
Result: golangci-lint run reports 0 issues.
Assisted-by: Kiro (AI assistant)
Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
nsmbot added a commit to networkservicemesh/cmd-nse-vfio that referenced this pull request Sep 2, 2026
@nsmbot NSMBot
Update go.mod and go.sum to latest version from networkservicemesh/sd…
492c7b0 
…k@main (#591)

PR link: networkservicemesh/sdk#1761

Commit: 8c8366a
Author: Laszlo Kiraly
Date: 2026-09-02 15:32:01 +0200
Message:
  - Migrate golangci-lint config to v2 and bump linter to v2.13.2 (#1761)
golangci-lint v1.64.2 (built with go1.24) fails on this repository under
Go 1.25: it errors on the "go 1.25" config target and exhibits pathological
memory use (>16GB, never completing) that causes the CI runner to be killed.
A release built with go1.25+ resolves both problems (completes in ~40s at
~1.5GB).
- Migrate .golangci.yml from the v1 to the v2 format and set run.go to "1.25".
- Bump linter-version in ci.yaml from v1.64.2 to v2.13.2 (built with go1.27)
  so CI runs the v2 linter against the v2 config atomically.
- Suppress noise introduced by v2's newer/stricter analyzers so the effective
  policy matches v1 behavior:
    * goconst: min-occurrences 2 -> 3; exclude test and testutil helpers
    * gosec: exclude G304/G702/G703 (file-inclusion and taint-analysis rules
      on process-controlled paths, not external input)
    * staticcheck: disable SA4023 (interface nil-comparison false positive)
      and QF1001/QF1003/QF1008/QF1012 (quickfix style suggestions)
    * govet: disable the new go1.27 "inline" analyzer
Result: golangci-lint run reports 0 issues.
Assisted-by: Kiro (AI assistant)

Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
Co-authored-by: NSMBot <nsmbot@networkservicmesh.io>
nsmbot added a commit to networkservicemesh/sdk-k8s that referenced this pull request Sep 2, 2026
@nsmbot NSMBot
Update go.mod and go.sum to latest version from networkservicemesh/sd…
4fb341c 
…k@main (#588)

PR link: networkservicemesh/sdk#1761

Commit: 8c8366a
Author: Laszlo Kiraly
Date: 2026-09-02 15:32:01 +0200
Message:
  - Migrate golangci-lint config to v2 and bump linter to v2.13.2 (#1761)
golangci-lint v1.64.2 (built with go1.24) fails on this repository under
Go 1.25: it errors on the "go 1.25" config target and exhibits pathological
memory use (>16GB, never completing) that causes the CI runner to be killed.
A release built with go1.25+ resolves both problems (completes in ~40s at
~1.5GB).
- Migrate .golangci.yml from the v1 to the v2 format and set run.go to "1.25".
- Bump linter-version in ci.yaml from v1.64.2 to v2.13.2 (built with go1.27)
  so CI runs the v2 linter against the v2 config atomically.
- Suppress noise introduced by v2's newer/stricter analyzers so the effective
  policy matches v1 behavior:
    * goconst: min-occurrences 2 -> 3; exclude test and testutil helpers
    * gosec: exclude G304/G702/G703 (file-inclusion and taint-analysis rules
      on process-controlled paths, not external input)
    * staticcheck: disable SA4023 (interface nil-comparison false positive)
      and QF1001/QF1003/QF1008/QF1012 (quickfix style suggestions)
    * govet: disable the new go1.27 "inline" analyzer
Result: golangci-lint run reports 0 issues.
Assisted-by: Kiro (AI assistant)

Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
Co-authored-by: NSMBot <nsmbot@networkservicmesh.io>
nsmbot added a commit to networkservicemesh/cmd-nse-supplier-k8s that referenced this pull request Sep 2, 2026
@nsmbot NSMBot
Update go.mod and go.sum to latest version from networkservicemesh/sd…
48c4af3 
…k-k8s@main (#406)

PR link: networkservicemesh/sdk-k8s#588

Commit: 4fb341c
Author: Network Service Mesh Bot
Date: 2026-09-02 08:45:45 -0500
Message:
  - Update go.mod and go.sum to latest version from networkservicemesh/sdk@main (#588)
PR link: networkservicemesh/sdk#1761
Commit: 8c8366a
Author: Laszlo Kiraly
Date: 2026-09-02 15:32:01 +0200
Message:
    - Migrate golangci-lint config to v2 and bump linter to v2.13.2 (#1761)
golangci-lint v1.64.2 (built with go1.24) fails on this repository under
Go 1.25: it errors on the "go 1.25" config target and exhibits pathological
memory use (>16GB, never completing) that causes the CI runner to be killed.
A release built with go1.25+ resolves both problems (completes in ~40s at
~1.5GB).
- Migrate .golangci.yml from the v1 to the v2 format and set run.go to "1.25".
- Bump linter-version in ci.yaml from v1.64.2 to v2.13.2 (built with go1.27)
  so CI runs the v2 linter against the v2 config atomically.
- Suppress noise introduced by v2's newer/stricter analyzers so the effective
  policy matches v1 behavior:
    * goconst: min-occurrences 2 -> 3; exclude test and testutil helpers
    * gosec: exclude G304/G702/G703 (file-inclusion and taint-analysis rules
      on process-controlled paths, not external input)
    * staticcheck: disable SA4023 (interface nil-comparison false positive)
      and QF1001/QF1003/QF1008/QF1012 (quickfix style suggestions)
    * govet: disable the new go1.27 "inline" analyzer
Result: golangci-lint run reports 0 issues.
Assisted-by: Kiro (AI assistant)

Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
Co-authored-by: NSMBot <nsmbot@networkservicmesh.io>
nsmbot pushed a commit to networkservicemesh/deployments-k8s that referenced this pull request Sep 2, 2026
NSMBot
Update go.mod and go.sum to latest version from networkservicemesh/cm…
83c41fd 
…d-admission-webhook-k8s@main

PR link: networkservicemesh/cmd-admission-webhook-k8s#512

Commit: 46c51d6
Author: Network Service Mesh Bot
Date: 2026-09-02 08:56:01 -0500
Message:
  - Update go.mod and go.sum to latest version from networkservicemesh/sdk-k8s@main (#512)
PR link: networkservicemesh/sdk-k8s#588
Commit: 4fb341c
Author: Network Service Mesh Bot
Date: 2026-09-02 08:45:45 -0500
Message:
    - Update go.mod and go.sum to latest version from networkservicemesh/sdk@main (#588)
PR link: networkservicemesh/sdk#1761
Commit: 8c8366a
Author: Laszlo Kiraly
Date: 2026-09-02 15:32:01 +0200
Message:
        - Migrate golangci-lint config to v2 and bump linter to v2.13.2 (#1761)
golangci-lint v1.64.2 (built with go1.24) fails on this repository under
Go 1.25: it errors on the "go 1.25" config target and exhibits pathological
memory use (>16GB, never completing) that causes the CI runner to be killed.
A release built with go1.25+ resolves both problems (completes in ~40s at
~1.5GB).
- Migrate .golangci.yml from the v1 to the v2 format and set run.go to "1.25".
- Bump linter-version in ci.yaml from v1.64.2 to v2.13.2 (built with go1.27)
  so CI runs the v2 linter against the v2 config atomically.
- Suppress noise introduced by v2's newer/stricter analyzers so the effective
  policy matches v1 behavior:
    * goconst: min-occurrences 2 -> 3; exclude test and testutil helpers
    * gosec: exclude G304/G702/G703 (file-inclusion and taint-analysis rules
      on process-controlled paths, not external input)
    * staticcheck: disable SA4023 (interface nil-comparison false positive)
      and QF1001/QF1003/QF1008/QF1012 (quickfix style suggestions)
    * govet: disable the new go1.27 "inline" analyzer
Result: golangci-lint run reports 0 issues.
Assisted-by: Kiro (AI assistant)
Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
nsmbot pushed a commit to networkservicemesh/deployments-k8s that referenced this pull request Sep 2, 2026
NSMBot
Update go.mod and go.sum to latest version from networkservicemesh/cm…
1cce64a 
…d-exclude-prefixes-k8s@main

PR link: networkservicemesh/cmd-exclude-prefixes-k8s#368

Commit: 7ac3880
Author: Network Service Mesh Bot
Date: 2026-09-02 08:56:10 -0500
Message:
  - Update go.mod and go.sum to latest version from networkservicemesh/sdk-k8s@main (#368)
PR link: networkservicemesh/sdk-k8s#588
Commit: 4fb341c
Author: Network Service Mesh Bot
Date: 2026-09-02 08:45:45 -0500
Message:
    - Update go.mod and go.sum to latest version from networkservicemesh/sdk@main (#588)
PR link: networkservicemesh/sdk#1761
Commit: 8c8366a
Author: Laszlo Kiraly
Date: 2026-09-02 15:32:01 +0200
Message:
        - Migrate golangci-lint config to v2 and bump linter to v2.13.2 (#1761)
golangci-lint v1.64.2 (built with go1.24) fails on this repository under
Go 1.25: it errors on the "go 1.25" config target and exhibits pathological
memory use (>16GB, never completing) that causes the CI runner to be killed.
A release built with go1.25+ resolves both problems (completes in ~40s at
~1.5GB).
- Migrate .golangci.yml from the v1 to the v2 format and set run.go to "1.25".
- Bump linter-version in ci.yaml from v1.64.2 to v2.13.2 (built with go1.27)
  so CI runs the v2 linter against the v2 config atomically.
- Suppress noise introduced by v2's newer/stricter analyzers so the effective
  policy matches v1 behavior:
    * goconst: min-occurrences 2 -> 3; exclude test and testutil helpers
    * gosec: exclude G304/G702/G703 (file-inclusion and taint-analysis rules
      on process-controlled paths, not external input)
    * staticcheck: disable SA4023 (interface nil-comparison false positive)
      and QF1001/QF1003/QF1008/QF1012 (quickfix style suggestions)
    * govet: disable the new go1.27 "inline" analyzer
Result: golangci-lint run reports 0 issues.
Assisted-by: Kiro (AI assistant)
Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
nsmbot pushed a commit to networkservicemesh/deployments-k8s that referenced this pull request Sep 2, 2026
NSMBot
Update go.mod and go.sum to latest version from networkservicemesh/cm…
99a0ec3 
…d-registry-k8s@main

PR link: networkservicemesh/cmd-registry-k8s#529

Commit: 906ff9a
Author: Network Service Mesh Bot
Date: 2026-09-02 08:56:22 -0500
Message:
  - Update go.mod and go.sum to latest version from networkservicemesh/sdk-k8s@main (#529)
PR link: networkservicemesh/sdk-k8s#588
Commit: 4fb341c
Author: Network Service Mesh Bot
Date: 2026-09-02 08:45:45 -0500
Message:
    - Update go.mod and go.sum to latest version from networkservicemesh/sdk@main (#588)
PR link: networkservicemesh/sdk#1761
Commit: 8c8366a
Author: Laszlo Kiraly
Date: 2026-09-02 15:32:01 +0200
Message:
        - Migrate golangci-lint config to v2 and bump linter to v2.13.2 (#1761)
golangci-lint v1.64.2 (built with go1.24) fails on this repository under
Go 1.25: it errors on the "go 1.25" config target and exhibits pathological
memory use (>16GB, never completing) that causes the CI runner to be killed.
A release built with go1.25+ resolves both problems (completes in ~40s at
~1.5GB).
- Migrate .golangci.yml from the v1 to the v2 format and set run.go to "1.25".
- Bump linter-version in ci.yaml from v1.64.2 to v2.13.2 (built with go1.27)
  so CI runs the v2 linter against the v2 config atomically.
- Suppress noise introduced by v2's newer/stricter analyzers so the effective
  policy matches v1 behavior:
    * goconst: min-occurrences 2 -> 3; exclude test and testutil helpers
    * gosec: exclude G304/G702/G703 (file-inclusion and taint-analysis rules
      on process-controlled paths, not external input)
    * staticcheck: disable SA4023 (interface nil-comparison false positive)
      and QF1001/QF1003/QF1008/QF1012 (quickfix style suggestions)
    * govet: disable the new go1.27 "inline" analyzer
Result: golangci-lint run reports 0 issues.
Assisted-by: Kiro (AI assistant)
Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
nsmbot pushed a commit to networkservicemesh/deployments-k8s that referenced this pull request Sep 2, 2026
NSMBot
Update go.mod and go.sum to latest version from networkservicemesh/cm…
5d22563 
…d-nse-supplier-k8s@main

PR link: networkservicemesh/cmd-nse-supplier-k8s#406

Commit: 48c4af3
Author: Network Service Mesh Bot
Date: 2026-09-02 08:57:50 -0500
Message:
  - Update go.mod and go.sum to latest version from networkservicemesh/sdk-k8s@main (#406)
PR link: networkservicemesh/sdk-k8s#588
Commit: 4fb341c
Author: Network Service Mesh Bot
Date: 2026-09-02 08:45:45 -0500
Message:
    - Update go.mod and go.sum to latest version from networkservicemesh/sdk@main (#588)
PR link: networkservicemesh/sdk#1761
Commit: 8c8366a
Author: Laszlo Kiraly
Date: 2026-09-02 15:32:01 +0200
Message:
        - Migrate golangci-lint config to v2 and bump linter to v2.13.2 (#1761)
golangci-lint v1.64.2 (built with go1.24) fails on this repository under
Go 1.25: it errors on the "go 1.25" config target and exhibits pathological
memory use (>16GB, never completing) that causes the CI runner to be killed.
A release built with go1.25+ resolves both problems (completes in ~40s at
~1.5GB).
- Migrate .golangci.yml from the v1 to the v2 format and set run.go to "1.25".
- Bump linter-version in ci.yaml from v1.64.2 to v2.13.2 (built with go1.27)
  so CI runs the v2 linter against the v2 config atomically.
- Suppress noise introduced by v2's newer/stricter analyzers so the effective
  policy matches v1 behavior:
    * goconst: min-occurrences 2 -> 3; exclude test and testutil helpers
    * gosec: exclude G304/G702/G703 (file-inclusion and taint-analysis rules
      on process-controlled paths, not external input)
    * staticcheck: disable SA4023 (interface nil-comparison false positive)
      and QF1001/QF1003/QF1008/QF1012 (quickfix style suggestions)
    * govet: disable the new go1.27 "inline" analyzer
Result: golangci-lint run reports 0 issues.
Assisted-by: Kiro (AI assistant)
Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
nsmbot added a commit to networkservicemesh/sdk-ovs that referenced this pull request Sep 2, 2026
@nsmbot NSMBot
Update go.mod and go.sum to latest version from networkservicemesh/sd…
25e70d7 
…k-sriov@main (#401)

PR link: networkservicemesh/sdk-sriov#677

Commit: 89910e7
Author: Network Service Mesh Bot
Date: 2026-09-02 08:51:11 -0500
Message:
  - Update go.mod and go.sum to latest version from networkservicemesh/sdk-kernel@main (#677)
PR link: networkservicemesh/sdk-kernel#748
Commit: 0f93066
Author: Network Service Mesh Bot
Date: 2026-09-02 08:44:25 -0500
Message:
    - Update go.mod and go.sum to latest version from networkservicemesh/sdk@main (#748)
PR link: networkservicemesh/sdk#1761
Commit: 8c8366a
Author: Laszlo Kiraly
Date: 2026-09-02 15:32:01 +0200
Message:
        - Migrate golangci-lint config to v2 and bump linter to v2.13.2 (#1761)
golangci-lint v1.64.2 (built with go1.24) fails on this repository under
Go 1.25: it errors on the "go 1.25" config target and exhibits pathological
memory use (>16GB, never completing) that causes the CI runner to be killed.
A release built with go1.25+ resolves both problems (completes in ~40s at
~1.5GB).
- Migrate .golangci.yml from the v1 to the v2 format and set run.go to "1.25".
- Bump linter-version in ci.yaml from v1.64.2 to v2.13.2 (built with go1.27)
  so CI runs the v2 linter against the v2 config atomically.
- Suppress noise introduced by v2's newer/stricter analyzers so the effective
  policy matches v1 behavior:
    * goconst: min-occurrences 2 -> 3; exclude test and testutil helpers
    * gosec: exclude G304/G702/G703 (file-inclusion and taint-analysis rules
      on process-controlled paths, not external input)
    * staticcheck: disable SA4023 (interface nil-comparison false positive)
      and QF1001/QF1003/QF1008/QF1012 (quickfix style suggestions)
    * govet: disable the new go1.27 "inline" analyzer
Result: golangci-lint run reports 0 issues.
Assisted-by: Kiro (AI assistant)

Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
Co-authored-by: NSMBot <nsmbot@networkservicmesh.io>
nsmbot added a commit to networkservicemesh/cmd-nse-vlan-vpp that referenced this pull request Sep 2, 2026
@nsmbot NSMBot
Update go.mod and go.sum to latest version from networkservicemesh/sd…
419221a 
…k-sriov@main (#623)

PR link: networkservicemesh/sdk-sriov#677

Commit: 89910e7
Author: Network Service Mesh Bot
Date: 2026-09-02 08:51:11 -0500
Message:
  - Update go.mod and go.sum to latest version from networkservicemesh/sdk-kernel@main (#677)
PR link: networkservicemesh/sdk-kernel#748
Commit: 0f93066
Author: Network Service Mesh Bot
Date: 2026-09-02 08:44:25 -0500
Message:
    - Update go.mod and go.sum to latest version from networkservicemesh/sdk@main (#748)
PR link: networkservicemesh/sdk#1761
Commit: 8c8366a
Author: Laszlo Kiraly
Date: 2026-09-02 15:32:01 +0200
Message:
        - Migrate golangci-lint config to v2 and bump linter to v2.13.2 (#1761)
golangci-lint v1.64.2 (built with go1.24) fails on this repository under
Go 1.25: it errors on the "go 1.25" config target and exhibits pathological
memory use (>16GB, never completing) that causes the CI runner to be killed.
A release built with go1.25+ resolves both problems (completes in ~40s at
~1.5GB).
- Migrate .golangci.yml from the v1 to the v2 format and set run.go to "1.25".
- Bump linter-version in ci.yaml from v1.64.2 to v2.13.2 (built with go1.27)
  so CI runs the v2 linter against the v2 config atomically.
- Suppress noise introduced by v2's newer/stricter analyzers so the effective
  policy matches v1 behavior:
    * goconst: min-occurrences 2 -> 3; exclude test and testutil helpers
    * gosec: exclude G304/G702/G703 (file-inclusion and taint-analysis rules
      on process-controlled paths, not external input)
    * staticcheck: disable SA4023 (interface nil-comparison false positive)
      and QF1001/QF1003/QF1008/QF1012 (quickfix style suggestions)
    * govet: disable the new go1.27 "inline" analyzer
Result: golangci-lint run reports 0 issues.
Assisted-by: Kiro (AI assistant)

Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
Co-authored-by: NSMBot <nsmbot@networkservicmesh.io>
nsmbot added a commit to networkservicemesh/deployments-k8s that referenced this pull request Sep 2, 2026
@nsmbot NSMBot
Update go.mod and go.sum to latest version from networkservicemesh/cm…
93a9aa4 
…d-admission-webhook-k8s@main (#13772)

PR link: networkservicemesh/cmd-admission-webhook-k8s#512

Commit: 46c51d6
Author: Network Service Mesh Bot
Date: 2026-09-02 08:56:01 -0500
Message:
  - Update go.mod and go.sum to latest version from networkservicemesh/sdk-k8s@main (#512)
PR link: networkservicemesh/sdk-k8s#588
Commit: 4fb341c
Author: Network Service Mesh Bot
Date: 2026-09-02 08:45:45 -0500
Message:
    - Update go.mod and go.sum to latest version from networkservicemesh/sdk@main (#588)
PR link: networkservicemesh/sdk#1761
Commit: 8c8366a
Author: Laszlo Kiraly
Date: 2026-09-02 15:32:01 +0200
Message:
        - Migrate golangci-lint config to v2 and bump linter to v2.13.2 (#1761)
golangci-lint v1.64.2 (built with go1.24) fails on this repository under
Go 1.25: it errors on the "go 1.25" config target and exhibits pathological
memory use (>16GB, never completing) that causes the CI runner to be killed.
A release built with go1.25+ resolves both problems (completes in ~40s at
~1.5GB).
- Migrate .golangci.yml from the v1 to the v2 format and set run.go to "1.25".
- Bump linter-version in ci.yaml from v1.64.2 to v2.13.2 (built with go1.27)
  so CI runs the v2 linter against the v2 config atomically.
- Suppress noise introduced by v2's newer/stricter analyzers so the effective
  policy matches v1 behavior:
    * goconst: min-occurrences 2 -> 3; exclude test and testutil helpers
    * gosec: exclude G304/G702/G703 (file-inclusion and taint-analysis rules
      on process-controlled paths, not external input)
    * staticcheck: disable SA4023 (interface nil-comparison false positive)
      and QF1001/QF1003/QF1008/QF1012 (quickfix style suggestions)
    * govet: disable the new go1.27 "inline" analyzer
Result: golangci-lint run reports 0 issues.
Assisted-by: Kiro (AI assistant)

Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
Co-authored-by: NSMBot <nsmbot@networkservicmesh.io>
nsmbot added a commit to networkservicemesh/cmd-nse-icmp-responder-vpp that referenced this pull request Sep 2, 2026
@nsmbot NSMBot
Update go.mod and go.sum to latest version from networkservicemesh/sd…
58aca21 
…k-vpp@main (#778)

PR link: networkservicemesh/sdk-vpp#925

Commit: 53fe741
Author: Network Service Mesh Bot
Date: 2026-09-02 08:51:24 -0500
Message:
  - Update go.mod and go.sum to latest version from networkservicemesh/sdk-kernel@main (#925)
PR link: networkservicemesh/sdk-kernel#748
Commit: 0f93066
Author: Network Service Mesh Bot
Date: 2026-09-02 08:44:25 -0500
Message:
    - Update go.mod and go.sum to latest version from networkservicemesh/sdk@main (#748)
PR link: networkservicemesh/sdk#1761
Commit: 8c8366a
Author: Laszlo Kiraly
Date: 2026-09-02 15:32:01 +0200
Message:
        - Migrate golangci-lint config to v2 and bump linter to v2.13.2 (#1761)
golangci-lint v1.64.2 (built with go1.24) fails on this repository under
Go 1.25: it errors on the "go 1.25" config target and exhibits pathological
memory use (>16GB, never completing) that causes the CI runner to be killed.
A release built with go1.25+ resolves both problems (completes in ~40s at
~1.5GB).
- Migrate .golangci.yml from the v1 to the v2 format and set run.go to "1.25".
- Bump linter-version in ci.yaml from v1.64.2 to v2.13.2 (built with go1.27)
  so CI runs the v2 linter against the v2 config atomically.
- Suppress noise introduced by v2's newer/stricter analyzers so the effective
  policy matches v1 behavior:
    * goconst: min-occurrences 2 -> 3; exclude test and testutil helpers
    * gosec: exclude G304/G702/G703 (file-inclusion and taint-analysis rules
      on process-controlled paths, not external input)
    * staticcheck: disable SA4023 (interface nil-comparison false positive)
      and QF1001/QF1003/QF1008/QF1012 (quickfix style suggestions)
    * govet: disable the new go1.27 "inline" analyzer
Result: golangci-lint run reports 0 issues.
Assisted-by: Kiro (AI assistant)

Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
Co-authored-by: NSMBot <nsmbot@networkservicmesh.io>
nsmbot added a commit to networkservicemesh/cmd-nsc-vpp that referenced this pull request Sep 2, 2026
@nsmbot NSMBot
Update go.mod and go.sum to latest version from networkservicemesh/sd…
c687c53 
…k-vpp@main (#794)

PR link: networkservicemesh/sdk-vpp#925

Commit: 53fe741
Author: Network Service Mesh Bot
Date: 2026-09-02 08:51:24 -0500
Message:
  - Update go.mod and go.sum to latest version from networkservicemesh/sdk-kernel@main (#925)
PR link: networkservicemesh/sdk-kernel#748
Commit: 0f93066
Author: Network Service Mesh Bot
Date: 2026-09-02 08:44:25 -0500
Message:
    - Update go.mod and go.sum to latest version from networkservicemesh/sdk@main (#748)
PR link: networkservicemesh/sdk#1761
Commit: 8c8366a
Author: Laszlo Kiraly
Date: 2026-09-02 15:32:01 +0200
Message:
        - Migrate golangci-lint config to v2 and bump linter to v2.13.2 (#1761)
golangci-lint v1.64.2 (built with go1.24) fails on this repository under
Go 1.25: it errors on the "go 1.25" config target and exhibits pathological
memory use (>16GB, never completing) that causes the CI runner to be killed.
A release built with go1.25+ resolves both problems (completes in ~40s at
~1.5GB).
- Migrate .golangci.yml from the v1 to the v2 format and set run.go to "1.25".
- Bump linter-version in ci.yaml from v1.64.2 to v2.13.2 (built with go1.27)
  so CI runs the v2 linter against the v2 config atomically.
- Suppress noise introduced by v2's newer/stricter analyzers so the effective
  policy matches v1 behavior:
    * goconst: min-occurrences 2 -> 3; exclude test and testutil helpers
    * gosec: exclude G304/G702/G703 (file-inclusion and taint-analysis rules
      on process-controlled paths, not external input)
    * staticcheck: disable SA4023 (interface nil-comparison false positive)
      and QF1001/QF1003/QF1008/QF1012 (quickfix style suggestions)
    * govet: disable the new go1.27 "inline" analyzer
Result: golangci-lint run reports 0 issues.
Assisted-by: Kiro (AI assistant)

Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
Co-authored-by: NSMBot <nsmbot@networkservicmesh.io>
nsmbot added a commit to networkservicemesh/deployments-k8s that referenced this pull request Sep 2, 2026
@nsmbot NSMBot
Update go.mod and go.sum to latest version from networkservicemesh/cm…
cc71e74 
…d-exclude-prefixes-k8s@main (#13743)

PR link: networkservicemesh/cmd-exclude-prefixes-k8s#368

Commit: 7ac3880
Author: Network Service Mesh Bot
Date: 2026-09-02 08:56:10 -0500
Message:
  - Update go.mod and go.sum to latest version from networkservicemesh/sdk-k8s@main (#368)
PR link: networkservicemesh/sdk-k8s#588
Commit: 4fb341c
Author: Network Service Mesh Bot
Date: 2026-09-02 08:45:45 -0500
Message:
    - Update go.mod and go.sum to latest version from networkservicemesh/sdk@main (#588)
PR link: networkservicemesh/sdk#1761
Commit: 8c8366a
Author: Laszlo Kiraly
Date: 2026-09-02 15:32:01 +0200
Message:
        - Migrate golangci-lint config to v2 and bump linter to v2.13.2 (#1761)
golangci-lint v1.64.2 (built with go1.24) fails on this repository under
Go 1.25: it errors on the "go 1.25" config target and exhibits pathological
memory use (>16GB, never completing) that causes the CI runner to be killed.
A release built with go1.25+ resolves both problems (completes in ~40s at
~1.5GB).
- Migrate .golangci.yml from the v1 to the v2 format and set run.go to "1.25".
- Bump linter-version in ci.yaml from v1.64.2 to v2.13.2 (built with go1.27)
  so CI runs the v2 linter against the v2 config atomically.
- Suppress noise introduced by v2's newer/stricter analyzers so the effective
  policy matches v1 behavior:
    * goconst: min-occurrences 2 -> 3; exclude test and testutil helpers
    * gosec: exclude G304/G702/G703 (file-inclusion and taint-analysis rules
      on process-controlled paths, not external input)
    * staticcheck: disable SA4023 (interface nil-comparison false positive)
      and QF1001/QF1003/QF1008/QF1012 (quickfix style suggestions)
    * govet: disable the new go1.27 "inline" analyzer
Result: golangci-lint run reports 0 issues.
Assisted-by: Kiro (AI assistant)

Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
Co-authored-by: NSMBot <nsmbot@networkservicmesh.io>
nsmbot added a commit to networkservicemesh/cmd-nsc that referenced this pull request Sep 2, 2026
@nsmbot NSMBot
Update go.mod and go.sum to latest version from networkservicemesh/sd…
f8bee50 
…k-sriov@main (#710)

PR link: networkservicemesh/sdk-sriov#677

Commit: 89910e7
Author: Network Service Mesh Bot
Date: 2026-09-02 08:51:11 -0500
Message:
  - Update go.mod and go.sum to latest version from networkservicemesh/sdk-kernel@main (#677)
PR link: networkservicemesh/sdk-kernel#748
Commit: 0f93066
Author: Network Service Mesh Bot
Date: 2026-09-02 08:44:25 -0500
Message:
    - Update go.mod and go.sum to latest version from networkservicemesh/sdk@main (#748)
PR link: networkservicemesh/sdk#1761
Commit: 8c8366a
Author: Laszlo Kiraly
Date: 2026-09-02 15:32:01 +0200
Message:
        - Migrate golangci-lint config to v2 and bump linter to v2.13.2 (#1761)
golangci-lint v1.64.2 (built with go1.24) fails on this repository under
Go 1.25: it errors on the "go 1.25" config target and exhibits pathological
memory use (>16GB, never completing) that causes the CI runner to be killed.
A release built with go1.25+ resolves both problems (completes in ~40s at
~1.5GB).
- Migrate .golangci.yml from the v1 to the v2 format and set run.go to "1.25".
- Bump linter-version in ci.yaml from v1.64.2 to v2.13.2 (built with go1.27)
  so CI runs the v2 linter against the v2 config atomically.
- Suppress noise introduced by v2's newer/stricter analyzers so the effective
  policy matches v1 behavior:
    * goconst: min-occurrences 2 -> 3; exclude test and testutil helpers
    * gosec: exclude G304/G702/G703 (file-inclusion and taint-analysis rules
      on process-controlled paths, not external input)
    * staticcheck: disable SA4023 (interface nil-comparison false positive)
      and QF1001/QF1003/QF1008/QF1012 (quickfix style suggestions)
    * govet: disable the new go1.27 "inline" analyzer
Result: golangci-lint run reports 0 issues.
Assisted-by: Kiro (AI assistant)

Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
Co-authored-by: NSMBot <nsmbot@networkservicmesh.io>
nsmbot added a commit to networkservicemesh/deployments-k8s that referenced this pull request Sep 2, 2026
@nsmbot NSMBot
Update go.mod and go.sum to latest version from networkservicemesh/cm…
178ef77 
…d-registry-k8s@main (#13762)

PR link: networkservicemesh/cmd-registry-k8s#529

Commit: 906ff9a
Author: Network Service Mesh Bot
Date: 2026-09-02 08:56:22 -0500
Message:
  - Update go.mod and go.sum to latest version from networkservicemesh/sdk-k8s@main (#529)
PR link: networkservicemesh/sdk-k8s#588
Commit: 4fb341c
Author: Network Service Mesh Bot
Date: 2026-09-02 08:45:45 -0500
Message:
    - Update go.mod and go.sum to latest version from networkservicemesh/sdk@main (#588)
PR link: networkservicemesh/sdk#1761
Commit: 8c8366a
Author: Laszlo Kiraly
Date: 2026-09-02 15:32:01 +0200
Message:
        - Migrate golangci-lint config to v2 and bump linter to v2.13.2 (#1761)
golangci-lint v1.64.2 (built with go1.24) fails on this repository under
Go 1.25: it errors on the "go 1.25" config target and exhibits pathological
memory use (>16GB, never completing) that causes the CI runner to be killed.
A release built with go1.25+ resolves both problems (completes in ~40s at
~1.5GB).
- Migrate .golangci.yml from the v1 to the v2 format and set run.go to "1.25".
- Bump linter-version in ci.yaml from v1.64.2 to v2.13.2 (built with go1.27)
  so CI runs the v2 linter against the v2 config atomically.
- Suppress noise introduced by v2's newer/stricter analyzers so the effective
  policy matches v1 behavior:
    * goconst: min-occurrences 2 -> 3; exclude test and testutil helpers
    * gosec: exclude G304/G702/G703 (file-inclusion and taint-analysis rules
      on process-controlled paths, not external input)
    * staticcheck: disable SA4023 (interface nil-comparison false positive)
      and QF1001/QF1003/QF1008/QF1012 (quickfix style suggestions)
    * govet: disable the new go1.27 "inline" analyzer
Result: golangci-lint run reports 0 issues.
Assisted-by: Kiro (AI assistant)

Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
Co-authored-by: NSMBot <nsmbot@networkservicmesh.io>
nsmbot added a commit to networkservicemesh/cmd-nse-firewall-vpp that referenced this pull request Sep 2, 2026
@nsmbot NSMBot
Update go.mod and go.sum to latest version from networkservicemesh/sd…
bfa4284 
…k-vpp@main (#611)

PR link: networkservicemesh/sdk-vpp#925

Commit: 53fe741
Author: Network Service Mesh Bot
Date: 2026-09-02 08:51:24 -0500
Message:
  - Update go.mod and go.sum to latest version from networkservicemesh/sdk-kernel@main (#925)
PR link: networkservicemesh/sdk-kernel#748
Commit: 0f93066
Author: Network Service Mesh Bot
Date: 2026-09-02 08:44:25 -0500
Message:
    - Update go.mod and go.sum to latest version from networkservicemesh/sdk@main (#748)
PR link: networkservicemesh/sdk#1761
Commit: 8c8366a
Author: Laszlo Kiraly
Date: 2026-09-02 15:32:01 +0200
Message:
        - Migrate golangci-lint config to v2 and bump linter to v2.13.2 (#1761)
golangci-lint v1.64.2 (built with go1.24) fails on this repository under
Go 1.25: it errors on the "go 1.25" config target and exhibits pathological
memory use (>16GB, never completing) that causes the CI runner to be killed.
A release built with go1.25+ resolves both problems (completes in ~40s at
~1.5GB).
- Migrate .golangci.yml from the v1 to the v2 format and set run.go to "1.25".
- Bump linter-version in ci.yaml from v1.64.2 to v2.13.2 (built with go1.27)
  so CI runs the v2 linter against the v2 config atomically.
- Suppress noise introduced by v2's newer/stricter analyzers so the effective
  policy matches v1 behavior:
    * goconst: min-occurrences 2 -> 3; exclude test and testutil helpers
    * gosec: exclude G304/G702/G703 (file-inclusion and taint-analysis rules
      on process-controlled paths, not external input)
    * staticcheck: disable SA4023 (interface nil-comparison false positive)
      and QF1001/QF1003/QF1008/QF1012 (quickfix style suggestions)
    * govet: disable the new go1.27 "inline" analyzer
Result: golangci-lint run reports 0 issues.
Assisted-by: Kiro (AI assistant)

Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
Co-authored-by: NSMBot <nsmbot@networkservicmesh.io>
nsmbot pushed a commit to networkservicemesh/deployments-k8s that referenced this pull request Sep 2, 2026
NSMBot
Update go.mod and go.sum to latest version from networkservicemesh/cm…
d3dbdf7 
…d-nse-vlan-vpp@main

PR link: networkservicemesh/cmd-nse-vlan-vpp#623

Commit: 419221a
Author: Network Service Mesh Bot
Date: 2026-09-02 09:37:45 -0500
Message:
  - Update go.mod and go.sum to latest version from networkservicemesh/sdk-sriov@main (#623)
PR link: networkservicemesh/sdk-sriov#677
Commit: 89910e7
Author: Network Service Mesh Bot
Date: 2026-09-02 08:51:11 -0500
Message:
    - Update go.mod and go.sum to latest version from networkservicemesh/sdk-kernel@main (#677)
PR link: networkservicemesh/sdk-kernel#748
Commit: 0f93066
Author: Network Service Mesh Bot
Date: 2026-09-02 08:44:25 -0500
Message:
        - Update go.mod and go.sum to latest version from networkservicemesh/sdk@main (#748)
PR link: networkservicemesh/sdk#1761
Commit: 8c8366a
Author: Laszlo Kiraly
Date: 2026-09-02 15:32:01 +0200
Message:
                - Migrate golangci-lint config to v2 and bump linter to v2.13.2 (#1761)
golangci-lint v1.64.2 (built with go1.24) fails on this repository under
Go 1.25: it errors on the "go 1.25" config target and exhibits pathological
memory use (>16GB, never completing) that causes the CI runner to be killed.
A release built with go1.25+ resolves both problems (completes in ~40s at
~1.5GB).
- Migrate .golangci.yml from the v1 to the v2 format and set run.go to "1.25".
- Bump linter-version in ci.yaml from v1.64.2 to v2.13.2 (built with go1.27)
  so CI runs the v2 linter against the v2 config atomically.
- Suppress noise introduced by v2's newer/stricter analyzers so the effective
  policy matches v1 behavior:
    * goconst: min-occurrences 2 -> 3; exclude test and testutil helpers
    * gosec: exclude G304/G702/G703 (file-inclusion and taint-analysis rules
      on process-controlled paths, not external input)
    * staticcheck: disable SA4023 (interface nil-comparison false positive)
      and QF1001/QF1003/QF1008/QF1012 (quickfix style suggestions)
    * govet: disable the new go1.27 "inline" analyzer
Result: golangci-lint run reports 0 issues.
Assisted-by: Kiro (AI assistant)
Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
nsmbot added a commit to networkservicemesh/cmd-nse-icmp-responder that referenced this pull request Sep 2, 2026
@nsmbot NSMBot
Update go.mod and go.sum to latest version from networkservicemesh/sd…
2b63aba 
…k-sriov@main (#678)

PR link: networkservicemesh/sdk-sriov#677

Commit: 89910e7
Author: Network Service Mesh Bot
Date: 2026-09-02 08:51:11 -0500
Message:
  - Update go.mod and go.sum to latest version from networkservicemesh/sdk-kernel@main (#677)
PR link: networkservicemesh/sdk-kernel#748
Commit: 0f93066
Author: Network Service Mesh Bot
Date: 2026-09-02 08:44:25 -0500
Message:
    - Update go.mod and go.sum to latest version from networkservicemesh/sdk@main (#748)
PR link: networkservicemesh/sdk#1761
Commit: 8c8366a
Author: Laszlo Kiraly
Date: 2026-09-02 15:32:01 +0200
Message:
        - Migrate golangci-lint config to v2 and bump linter to v2.13.2 (#1761)
golangci-lint v1.64.2 (built with go1.24) fails on this repository under
Go 1.25: it errors on the "go 1.25" config target and exhibits pathological
memory use (>16GB, never completing) that causes the CI runner to be killed.
A release built with go1.25+ resolves both problems (completes in ~40s at
~1.5GB).
- Migrate .golangci.yml from the v1 to the v2 format and set run.go to "1.25".
- Bump linter-version in ci.yaml from v1.64.2 to v2.13.2 (built with go1.27)
  so CI runs the v2 linter against the v2 config atomically.
- Suppress noise introduced by v2's newer/stricter analyzers so the effective
  policy matches v1 behavior:
    * goconst: min-occurrences 2 -> 3; exclude test and testutil helpers
    * gosec: exclude G304/G702/G703 (file-inclusion and taint-analysis rules
      on process-controlled paths, not external input)
    * staticcheck: disable SA4023 (interface nil-comparison false positive)
      and QF1001/QF1003/QF1008/QF1012 (quickfix style suggestions)
    * govet: disable the new go1.27 "inline" analyzer
Result: golangci-lint run reports 0 issues.
Assisted-by: Kiro (AI assistant)

Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
Co-authored-by: NSMBot <nsmbot@networkservicmesh.io>
nsmbot added a commit to networkservicemesh/cmd-lb-vl3-vpp that referenced this pull request Sep 2, 2026
@nsmbot NSMBot
Update go.mod and go.sum to latest version from networkservicemesh/sd…
ad5c424 
…k-vpp@main (#169)

PR link: networkservicemesh/sdk-vpp#925

Commit: 53fe741
Author: Network Service Mesh Bot
Date: 2026-09-02 08:51:24 -0500
Message:
  - Update go.mod and go.sum to latest version from networkservicemesh/sdk-kernel@main (#925)
PR link: networkservicemesh/sdk-kernel#748
Commit: 0f93066
Author: Network Service Mesh Bot
Date: 2026-09-02 08:44:25 -0500
Message:
    - Update go.mod and go.sum to latest version from networkservicemesh/sdk@main (#748)
PR link: networkservicemesh/sdk#1761
Commit: 8c8366a
Author: Laszlo Kiraly
Date: 2026-09-02 15:32:01 +0200
Message:
        - Migrate golangci-lint config to v2 and bump linter to v2.13.2 (#1761)
golangci-lint v1.64.2 (built with go1.24) fails on this repository under
Go 1.25: it errors on the "go 1.25" config target and exhibits pathological
memory use (>16GB, never completing) that causes the CI runner to be killed.
A release built with go1.25+ resolves both problems (completes in ~40s at
~1.5GB).
- Migrate .golangci.yml from the v1 to the v2 format and set run.go to "1.25".
- Bump linter-version in ci.yaml from v1.64.2 to v2.13.2 (built with go1.27)
  so CI runs the v2 linter against the v2 config atomically.
- Suppress noise introduced by v2's newer/stricter analyzers so the effective
  policy matches v1 behavior:
    * goconst: min-occurrences 2 -> 3; exclude test and testutil helpers
    * gosec: exclude G304/G702/G703 (file-inclusion and taint-analysis rules
      on process-controlled paths, not external input)
    * staticcheck: disable SA4023 (interface nil-comparison false positive)
      and QF1001/QF1003/QF1008/QF1012 (quickfix style suggestions)
    * govet: disable the new go1.27 "inline" analyzer
Result: golangci-lint run reports 0 issues.
Assisted-by: Kiro (AI assistant)

Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
Co-authored-by: NSMBot <nsmbot@networkservicmesh.io>
nsmbot added a commit to networkservicemesh/cmd-nse-simple-vl3-docker that referenced this pull request Sep 2, 2026
@nsmbot NSMBot
Update go.mod and go.sum to latest version from networkservicemesh/sd…
a5ab31f 
…k-vpp@main (#339)

PR link: networkservicemesh/sdk-vpp#925

Commit: 53fe741
Author: Network Service Mesh Bot
Date: 2026-09-02 08:51:24 -0500
Message:
  - Update go.mod and go.sum to latest version from networkservicemesh/sdk-kernel@main (#925)
PR link: networkservicemesh/sdk-kernel#748
Commit: 0f93066
Author: Network Service Mesh Bot
Date: 2026-09-02 08:44:25 -0500
Message:
    - Update go.mod and go.sum to latest version from networkservicemesh/sdk@main (#748)
PR link: networkservicemesh/sdk#1761
Commit: 8c8366a
Author: Laszlo Kiraly
Date: 2026-09-02 15:32:01 +0200
Message:
        - Migrate golangci-lint config to v2 and bump linter to v2.13.2 (#1761)
golangci-lint v1.64.2 (built with go1.24) fails on this repository under
Go 1.25: it errors on the "go 1.25" config target and exhibits pathological
memory use (>16GB, never completing) that causes the CI runner to be killed.
A release built with go1.25+ resolves both problems (completes in ~40s at
~1.5GB).
- Migrate .golangci.yml from the v1 to the v2 format and set run.go to "1.25".
- Bump linter-version in ci.yaml from v1.64.2 to v2.13.2 (built with go1.27)
  so CI runs the v2 linter against the v2 config atomically.
- Suppress noise introduced by v2's newer/stricter analyzers so the effective
  policy matches v1 behavior:
    * goconst: min-occurrences 2 -> 3; exclude test and testutil helpers
    * gosec: exclude G304/G702/G703 (file-inclusion and taint-analysis rules
      on process-controlled paths, not external input)
    * staticcheck: disable SA4023 (interface nil-comparison false positive)
      and QF1001/QF1003/QF1008/QF1012 (quickfix style suggestions)
    * govet: disable the new go1.27 "inline" analyzer
Result: golangci-lint run reports 0 issues.
Assisted-by: Kiro (AI assistant)

Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
Co-authored-by: NSMBot <nsmbot@networkservicmesh.io>
nsmbot added a commit to networkservicemesh/deployments-k8s that referenced this pull request Sep 2, 2026
@nsmbot NSMBot
Update go.mod and go.sum to latest version from networkservicemesh/cm…
9a3ce22 
…d-nse-supplier-k8s@main (#13751)

PR link: networkservicemesh/cmd-nse-supplier-k8s#406

Commit: 48c4af3
Author: Network Service Mesh Bot
Date: 2026-09-02 08:57:50 -0500
Message:
  - Update go.mod and go.sum to latest version from networkservicemesh/sdk-k8s@main (#406)
PR link: networkservicemesh/sdk-k8s#588
Commit: 4fb341c
Author: Network Service Mesh Bot
Date: 2026-09-02 08:45:45 -0500
Message:
    - Update go.mod and go.sum to latest version from networkservicemesh/sdk@main (#588)
PR link: networkservicemesh/sdk#1761
Commit: 8c8366a
Author: Laszlo Kiraly
Date: 2026-09-02 15:32:01 +0200
Message:
        - Migrate golangci-lint config to v2 and bump linter to v2.13.2 (#1761)
golangci-lint v1.64.2 (built with go1.24) fails on this repository under
Go 1.25: it errors on the "go 1.25" config target and exhibits pathological
memory use (>16GB, never completing) that causes the CI runner to be killed.
A release built with go1.25+ resolves both problems (completes in ~40s at
~1.5GB).
- Migrate .golangci.yml from the v1 to the v2 format and set run.go to "1.25".
- Bump linter-version in ci.yaml from v1.64.2 to v2.13.2 (built with go1.27)
  so CI runs the v2 linter against the v2 config atomically.
- Suppress noise introduced by v2's newer/stricter analyzers so the effective
  policy matches v1 behavior:
    * goconst: min-occurrences 2 -> 3; exclude test and testutil helpers
    * gosec: exclude G304/G702/G703 (file-inclusion and taint-analysis rules
      on process-controlled paths, not external input)
    * staticcheck: disable SA4023 (interface nil-comparison false positive)
      and QF1001/QF1003/QF1008/QF1012 (quickfix style suggestions)
    * govet: disable the new go1.27 "inline" analyzer
Result: golangci-lint run reports 0 issues.
Assisted-by: Kiro (AI assistant)

Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
Co-authored-by: NSMBot <nsmbot@networkservicmesh.io>
nsmbot added a commit to networkservicemesh/cmd-nse-vl3-vpp that referenced this pull request Sep 2, 2026
@nsmbot NSMBot
Update go.mod and go.sum to latest version from networkservicemesh/sd…
c3056d3 
…k-vpp@main (#437)

PR link: networkservicemesh/sdk-vpp#925

Commit: 53fe741
Author: Network Service Mesh Bot
Date: 2026-09-02 08:51:24 -0500
Message:
  - Update go.mod and go.sum to latest version from networkservicemesh/sdk-kernel@main (#925)
PR link: networkservicemesh/sdk-kernel#748
Commit: 0f93066
Author: Network Service Mesh Bot
Date: 2026-09-02 08:44:25 -0500
Message:
    - Update go.mod and go.sum to latest version from networkservicemesh/sdk@main (#748)
PR link: networkservicemesh/sdk#1761
Commit: 8c8366a
Author: Laszlo Kiraly
Date: 2026-09-02 15:32:01 +0200
Message:
        - Migrate golangci-lint config to v2 and bump linter to v2.13.2 (#1761)
golangci-lint v1.64.2 (built with go1.24) fails on this repository under
Go 1.25: it errors on the "go 1.25" config target and exhibits pathological
memory use (>16GB, never completing) that causes the CI runner to be killed.
A release built with go1.25+ resolves both problems (completes in ~40s at
~1.5GB).
- Migrate .golangci.yml from the v1 to the v2 format and set run.go to "1.25".
- Bump linter-version in ci.yaml from v1.64.2 to v2.13.2 (built with go1.27)
  so CI runs the v2 linter against the v2 config atomically.
- Suppress noise introduced by v2's newer/stricter analyzers so the effective
  policy matches v1 behavior:
    * goconst: min-occurrences 2 -> 3; exclude test and testutil helpers
    * gosec: exclude G304/G702/G703 (file-inclusion and taint-analysis rules
      on process-controlled paths, not external input)
    * staticcheck: disable SA4023 (interface nil-comparison false positive)
      and QF1001/QF1003/QF1008/QF1012 (quickfix style suggestions)
    * govet: disable the new go1.27 "inline" analyzer
Result: golangci-lint run reports 0 issues.
Assisted-by: Kiro (AI assistant)

Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
Co-authored-by: NSMBot <nsmbot@networkservicmesh.io>
nsmbot pushed a commit to networkservicemesh/deployments-k8s that referenced this pull request Sep 2, 2026
NSMBot
Update go.mod and go.sum to latest version from networkservicemesh/cm…
907d54b 
…d-nse-icmp-responder-vpp@main

PR link: networkservicemesh/cmd-nse-icmp-responder-vpp#778

Commit: 58aca21
Author: Network Service Mesh Bot
Date: 2026-09-02 09:58:36 -0500
Message:
  - Update go.mod and go.sum to latest version from networkservicemesh/sdk-vpp@main (#778)
PR link: networkservicemesh/sdk-vpp#925
Commit: 53fe741
Author: Network Service Mesh Bot
Date: 2026-09-02 08:51:24 -0500
Message:
    - Update go.mod and go.sum to latest version from networkservicemesh/sdk-kernel@main (#925)
PR link: networkservicemesh/sdk-kernel#748
Commit: 0f93066
Author: Network Service Mesh Bot
Date: 2026-09-02 08:44:25 -0500
Message:
        - Update go.mod and go.sum to latest version from networkservicemesh/sdk@main (#748)
PR link: networkservicemesh/sdk#1761
Commit: 8c8366a
Author: Laszlo Kiraly
Date: 2026-09-02 15:32:01 +0200
Message:
                - Migrate golangci-lint config to v2 and bump linter to v2.13.2 (#1761)
golangci-lint v1.64.2 (built with go1.24) fails on this repository under
Go 1.25: it errors on the "go 1.25" config target and exhibits pathological
memory use (>16GB, never completing) that causes the CI runner to be killed.
A release built with go1.25+ resolves both problems (completes in ~40s at
~1.5GB).
- Migrate .golangci.yml from the v1 to the v2 format and set run.go to "1.25".
- Bump linter-version in ci.yaml from v1.64.2 to v2.13.2 (built with go1.27)
  so CI runs the v2 linter against the v2 config atomically.
- Suppress noise introduced by v2's newer/stricter analyzers so the effective
  policy matches v1 behavior:
    * goconst: min-occurrences 2 -> 3; exclude test and testutil helpers
    * gosec: exclude G304/G702/G703 (file-inclusion and taint-analysis rules
      on process-controlled paths, not external input)
    * staticcheck: disable SA4023 (interface nil-comparison false positive)
      and QF1001/QF1003/QF1008/QF1012 (quickfix style suggestions)
    * govet: disable the new go1.27 "inline" analyzer
Result: golangci-lint run reports 0 issues.
Assisted-by: Kiro (AI assistant)
Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
nsmbot pushed a commit to networkservicemesh/deployments-k8s that referenced this pull request Sep 2, 2026
NSMBot
Update go.mod and go.sum to latest version from networkservicemesh/cm…
6ff01ad 
…d-nsc-vpp@main

PR link: networkservicemesh/cmd-nsc-vpp#794

Commit: c687c53
Author: Network Service Mesh Bot
Date: 2026-09-02 10:05:11 -0500
Message:
  - Update go.mod and go.sum to latest version from networkservicemesh/sdk-vpp@main (#794)
PR link: networkservicemesh/sdk-vpp#925
Commit: 53fe741
Author: Network Service Mesh Bot
Date: 2026-09-02 08:51:24 -0500
Message:
    - Update go.mod and go.sum to latest version from networkservicemesh/sdk-kernel@main (#925)
PR link: networkservicemesh/sdk-kernel#748
Commit: 0f93066
Author: Network Service Mesh Bot
Date: 2026-09-02 08:44:25 -0500
Message:
        - Update go.mod and go.sum to latest version from networkservicemesh/sdk@main (#748)
PR link: networkservicemesh/sdk#1761
Commit: 8c8366a
Author: Laszlo Kiraly
Date: 2026-09-02 15:32:01 +0200
Message:
                - Migrate golangci-lint config to v2 and bump linter to v2.13.2 (#1761)
golangci-lint v1.64.2 (built with go1.24) fails on this repository under
Go 1.25: it errors on the "go 1.25" config target and exhibits pathological
memory use (>16GB, never completing) that causes the CI runner to be killed.
A release built with go1.25+ resolves both problems (completes in ~40s at
~1.5GB).
- Migrate .golangci.yml from the v1 to the v2 format and set run.go to "1.25".
- Bump linter-version in ci.yaml from v1.64.2 to v2.13.2 (built with go1.27)
  so CI runs the v2 linter against the v2 config atomically.
- Suppress noise introduced by v2's newer/stricter analyzers so the effective
  policy matches v1 behavior:
    * goconst: min-occurrences 2 -> 3; exclude test and testutil helpers
    * gosec: exclude G304/G702/G703 (file-inclusion and taint-analysis rules
      on process-controlled paths, not external input)
    * staticcheck: disable SA4023 (interface nil-comparison false positive)
      and QF1001/QF1003/QF1008/QF1012 (quickfix style suggestions)
    * govet: disable the new go1.27 "inline" analyzer
Result: golangci-lint run reports 0 issues.
Assisted-by: Kiro (AI assistant)
Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
nsmbot pushed a commit to networkservicemesh/deployments-k8s that referenced this pull request Sep 2, 2026
NSMBot
Update go.mod and go.sum to latest version from networkservicemesh/cm…
e227ecf 
…d-nsc@main

PR link: networkservicemesh/cmd-nsc#710

Commit: f8bee50
Author: Network Service Mesh Bot
Date: 2026-09-02 10:15:06 -0500
Message:
  - Update go.mod and go.sum to latest version from networkservicemesh/sdk-sriov@main (#710)
PR link: networkservicemesh/sdk-sriov#677
Commit: 89910e7
Author: Network Service Mesh Bot
Date: 2026-09-02 08:51:11 -0500
Message:
    - Update go.mod and go.sum to latest version from networkservicemesh/sdk-kernel@main (#677)
PR link: networkservicemesh/sdk-kernel#748
Commit: 0f93066
Author: Network Service Mesh Bot
Date: 2026-09-02 08:44:25 -0500
Message:
        - Update go.mod and go.sum to latest version from networkservicemesh/sdk@main (#748)
PR link: networkservicemesh/sdk#1761
Commit: 8c8366a
Author: Laszlo Kiraly
Date: 2026-09-02 15:32:01 +0200
Message:
                - Migrate golangci-lint config to v2 and bump linter to v2.13.2 (#1761)
golangci-lint v1.64.2 (built with go1.24) fails on this repository under
Go 1.25: it errors on the "go 1.25" config target and exhibits pathological
memory use (>16GB, never completing) that causes the CI runner to be killed.
A release built with go1.25+ resolves both problems (completes in ~40s at
~1.5GB).
- Migrate .golangci.yml from the v1 to the v2 format and set run.go to "1.25".
- Bump linter-version in ci.yaml from v1.64.2 to v2.13.2 (built with go1.27)
  so CI runs the v2 linter against the v2 config atomically.
- Suppress noise introduced by v2's newer/stricter analyzers so the effective
  policy matches v1 behavior:
    * goconst: min-occurrences 2 -> 3; exclude test and testutil helpers
    * gosec: exclude G304/G702/G703 (file-inclusion and taint-analysis rules
      on process-controlled paths, not external input)
    * staticcheck: disable SA4023 (interface nil-comparison false positive)
      and QF1001/QF1003/QF1008/QF1012 (quickfix style suggestions)
    * govet: disable the new go1.27 "inline" analyzer
Result: golangci-lint run reports 0 issues.
Assisted-by: Kiro (AI assistant)
Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
nsmbot pushed a commit to networkservicemesh/deployments-k8s that referenced this pull request Sep 2, 2026
NSMBot
Update go.mod and go.sum to latest version from networkservicemesh/cm…
96b8af7 
…d-nse-firewall-vpp@main

PR link: networkservicemesh/cmd-nse-firewall-vpp#611

Commit: bfa4284
Author: Network Service Mesh Bot
Date: 2026-09-02 10:15:56 -0500
Message:
  - Update go.mod and go.sum to latest version from networkservicemesh/sdk-vpp@main (#611)
PR link: networkservicemesh/sdk-vpp#925
Commit: 53fe741
Author: Network Service Mesh Bot
Date: 2026-09-02 08:51:24 -0500
Message:
    - Update go.mod and go.sum to latest version from networkservicemesh/sdk-kernel@main (#925)
PR link: networkservicemesh/sdk-kernel#748
Commit: 0f93066
Author: Network Service Mesh Bot
Date: 2026-09-02 08:44:25 -0500
Message:
        - Update go.mod and go.sum to latest version from networkservicemesh/sdk@main (#748)
PR link: networkservicemesh/sdk#1761
Commit: 8c8366a
Author: Laszlo Kiraly
Date: 2026-09-02 15:32:01 +0200
Message:
                - Migrate golangci-lint config to v2 and bump linter to v2.13.2 (#1761)
golangci-lint v1.64.2 (built with go1.24) fails on this repository under
Go 1.25: it errors on the "go 1.25" config target and exhibits pathological
memory use (>16GB, never completing) that causes the CI runner to be killed.
A release built with go1.25+ resolves both problems (completes in ~40s at
~1.5GB).
- Migrate .golangci.yml from the v1 to the v2 format and set run.go to "1.25".
- Bump linter-version in ci.yaml from v1.64.2 to v2.13.2 (built with go1.27)
  so CI runs the v2 linter against the v2 config atomically.
- Suppress noise introduced by v2's newer/stricter analyzers so the effective
  policy matches v1 behavior:
    * goconst: min-occurrences 2 -> 3; exclude test and testutil helpers
    * gosec: exclude G304/G702/G703 (file-inclusion and taint-analysis rules
      on process-controlled paths, not external input)
    * staticcheck: disable SA4023 (interface nil-comparison false positive)
      and QF1001/QF1003/QF1008/QF1012 (quickfix style suggestions)
    * govet: disable the new go1.27 "inline" analyzer
Result: golangci-lint run reports 0 issues.
Assisted-by: Kiro (AI assistant)
Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
nsmbot pushed a commit to networkservicemesh/cmd-forwarder-ovs that referenced this pull request Sep 2, 2026
NSMBot
Update go.mod and go.sum to latest version from networkservicemesh/sd…
844a13b 
…k-ovs@main

PR link: networkservicemesh/sdk-ovs#401

Commit: 25e70d7
Author: Network Service Mesh Bot
Date: 2026-09-02 09:36:55 -0500
Message:
  - Update go.mod and go.sum to latest version from networkservicemesh/sdk-sriov@main (#401)
PR link: networkservicemesh/sdk-sriov#677
Commit: 89910e7
Author: Network Service Mesh Bot
Date: 2026-09-02 08:51:11 -0500
Message:
    - Update go.mod and go.sum to latest version from networkservicemesh/sdk-kernel@main (#677)
PR link: networkservicemesh/sdk-kernel#748
Commit: 0f93066
Author: Network Service Mesh Bot
Date: 2026-09-02 08:44:25 -0500
Message:
        - Update go.mod and go.sum to latest version from networkservicemesh/sdk@main (#748)
PR link: networkservicemesh/sdk#1761
Commit: 8c8366a
Author: Laszlo Kiraly
Date: 2026-09-02 15:32:01 +0200
Message:
                - Migrate golangci-lint config to v2 and bump linter to v2.13.2 (#1761)
golangci-lint v1.64.2 (built with go1.24) fails on this repository under
Go 1.25: it errors on the "go 1.25" config target and exhibits pathological
memory use (>16GB, never completing) that causes the CI runner to be killed.
A release built with go1.25+ resolves both problems (completes in ~40s at
~1.5GB).
- Migrate .golangci.yml from the v1 to the v2 format and set run.go to "1.25".
- Bump linter-version in ci.yaml from v1.64.2 to v2.13.2 (built with go1.27)
  so CI runs the v2 linter against the v2 config atomically.
- Suppress noise introduced by v2's newer/stricter analyzers so the effective
  policy matches v1 behavior:
    * goconst: min-occurrences 2 -> 3; exclude test and testutil helpers
    * gosec: exclude G304/G702/G703 (file-inclusion and taint-analysis rules
      on process-controlled paths, not external input)
    * staticcheck: disable SA4023 (interface nil-comparison false positive)
      and QF1001/QF1003/QF1008/QF1012 (quickfix style suggestions)
    * govet: disable the new go1.27 "inline" analyzer
Result: golangci-lint run reports 0 issues.
Assisted-by: Kiro (AI assistant)
Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
nsmbot pushed a commit to networkservicemesh/deployments-k8s that referenced this pull request Sep 2, 2026
NSMBot
Update go.mod and go.sum to latest version from networkservicemesh/cm…
bb2d544 
…d-nse-simple-vl3-docker@main

PR link: networkservicemesh/cmd-nse-simple-vl3-docker#339

Commit: a5ab31f
Author: Network Service Mesh Bot
Date: 2026-09-02 10:34:32 -0500
Message:
  - Update go.mod and go.sum to latest version from networkservicemesh/sdk-vpp@main (#339)
PR link: networkservicemesh/sdk-vpp#925
Commit: 53fe741
Author: Network Service Mesh Bot
Date: 2026-09-02 08:51:24 -0500
Message:
    - Update go.mod and go.sum to latest version from networkservicemesh/sdk-kernel@main (#925)
PR link: networkservicemesh/sdk-kernel#748
Commit: 0f93066
Author: Network Service Mesh Bot
Date: 2026-09-02 08:44:25 -0500
Message:
        - Update go.mod and go.sum to latest version from networkservicemesh/sdk@main (#748)
PR link: networkservicemesh/sdk#1761
Commit: 8c8366a
Author: Laszlo Kiraly
Date: 2026-09-02 15:32:01 +0200
Message:
                - Migrate golangci-lint config to v2 and bump linter to v2.13.2 (#1761)
golangci-lint v1.64.2 (built with go1.24) fails on this repository under
Go 1.25: it errors on the "go 1.25" config target and exhibits pathological
memory use (>16GB, never completing) that causes the CI runner to be killed.
A release built with go1.25+ resolves both problems (completes in ~40s at
~1.5GB).
- Migrate .golangci.yml from the v1 to the v2 format and set run.go to "1.25".
- Bump linter-version in ci.yaml from v1.64.2 to v2.13.2 (built with go1.27)
  so CI runs the v2 linter against the v2 config atomically.
- Suppress noise introduced by v2's newer/stricter analyzers so the effective
  policy matches v1 behavior:
    * goconst: min-occurrences 2 -> 3; exclude test and testutil helpers
    * gosec: exclude G304/G702/G703 (file-inclusion and taint-analysis rules
      on process-controlled paths, not external input)
    * staticcheck: disable SA4023 (interface nil-comparison false positive)
      and QF1001/QF1003/QF1008/QF1012 (quickfix style suggestions)
    * govet: disable the new go1.27 "inline" analyzer
Result: golangci-lint run reports 0 issues.
Assisted-by: Kiro (AI assistant)
Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
This was referenced Sep 2, 2026
Merged
Closed
Merged
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@szvincze szvincze szvincze approved these changes
@zolug zolug Awaiting requested review from zolug

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@ljkiraly @szvincze