[dray92]

Release v0.1.25 of zxporter, published from the internal services monorepo.

The v0.1.25 tag has already been created and points at this branch's tip — ArgoCD and other tag consumers can use it immediately. This PR is only to advance public main to the released commit for browser convenience.

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}

[gitar-bot]

CI failed: The golangci-lint job failed on 'lll' (line length) violations in chart test files, including helm-chart/zxporter-netmon/chart_globals_test.go, where a line is 122 characters against a 120 limit; this is directly tied to the change and is a simple formatting fix.

Overview

One unique error template was found across 1 analyzed log (job 116696127579, commit d4c25c2). The failure is a single lint-stage issue: the golangci-lint job reported lll line-length violations in chart tests. Overall assessment: a real, change-related failure that is easy to fix.

Failures

Line-length (lll) violations in chart tests (confidence: high)

• Type: tooling
• Affected jobs: 116696127579
• Related to change: yes
• Root cause: golangci-lint's lll linter flagged multiple lines exceeding the 120-character limit in chart test files, including helm-chart/zxporter-netmon/chart_globals_test.go:13 (122 characters). The PR adds these test files, so the violations are introduced by this change.
• Suggested fix: Wrap the overlong lines in the reported chart test files to stay within 120 characters, then rerun golangci-lint locally (golangci-lint run --new-from-rev=<base>) to confirm the job passes.

Summary

• Change-related failures: 1 finding (lll line-length violations in chart tests, related to this PR).
• Infrastructure/flaky failures: None identified. Deprecation and Node.js warnings in the log were excluded as non-blocking.
• Recommended action: Reformat the flagged lines in the chart test files (e.g., split long function calls and table-driven test literals across multiple lines), then push and confirm the golangci-lint job passes.

Code Review ✅ Approved

🔴 High risk · Adding Kubernetes read permissions and changing cluster-token resolution and persistence could expose additional cluster data or persist an unintended credential.

Release commit advancing public main to the v0.1.25 tag, which already points at this branch tip for tag consumers. No issues found.

Verification

Rules No rules evaluated

Functional validation Not enabled

Set up

Auto-approval Approved

_{For more verification details, comment gitar display:verbose.}

Tip

Comment Gitar fix CI or enable auto-apply: gitar auto-apply:on

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing compact verification results.

Comment with these commands to change the behavior for this request:

Auto-apply	Compact
gitar auto-apply:on	gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar}

[gitar-bot]

Gitar has auto-approved this PR (configure)