Skip to content

chore(release): v0.1.21 - #537

Open
dray92 wants to merge 1 commit into
mainfrom
release/v0.1.21
Open

dray92 wants to merge 1 commit into
mainfrom
release/v0.1.21

Conversation

@dray92

@dray92 dray92 commented Oct 7, 2026 •

Copy link
Copy Markdown
Contributor

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

The v0.1.21 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.


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

@gitar-bot

gitar-bot Bot commented Oct 7, 2026 •

Copy link
Copy Markdown
CI failed: Golangci-lint failed because a line length exceeds the 120-character limit in a new Helm chart test file.

Overview

1 failure found in total logs, caused by a linter rule violation in a newly added file.

Failures

Golangci-Lint Line Length Violation (confidence: high)

  • Type: tooling
  • Affected jobs: 113006799227
  • Related to change: yes
  • Root cause: The lll linter reports that helm-chart/zxporter/chart_topology_spread_test.go:12 is 162 characters long because the hostnameSpread JSON literal exceeds the 120-character maximum.
  • Suggested fix: Reformat the hostnameSpread JSON literal across multiple lines so no source line exceeds 120 characters, then rerun golangci-lint.

Summary

  • Change-related failures: 1 linter failure due to a line length violation in the PR diff.
  • Infrastructure/flaky failures: 0
  • Recommended action: Wrap or split the long JSON string literal in helm-chart/zxporter/chart_topology_spread_test.go to satisfy the lll linter rules.
Code Review ✅ Approved

🔴 High risk · The new scheduler scraper sends zxporter’s ServiceAccount token with TLS verification disabled, so interception could expose cluster credentials.

Release v0.1.21 advance to main — the tag is already created and in use by ArgoCD and other consumers. No issues found.

Auto-approved: No blocking issues found.
Please see Auto-approve Docs for details on setting custom approval criteria.

Review coverage

🤖 Auto-approval Approved

📋 Rules No rules evaluated

🧪 Functional validation Not enabled · Set up

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 → Counting what did not apply, without listing it.

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-bot Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Gitar has auto-approved this PR (configure)

@gitar-bot gitar-bot Bot added the gitar-approved Added by Gitar label Oct 7, 2026
if err == nil && pool.AppendCertsFromPEM(caData) {
tlsConfig.RootCAs = pool
} else {
tlsConfig.InsecureSkipVerify = true //nolint:gosec // see schedulerMetricsCAFileEnv doc comment.
tlsConfig.InsecureSkipVerify = true //nolint:gosec // see schedulerMetricsCAFileEnv doc comment.
}
} else {
tlsConfig.InsecureSkipVerify = true //nolint:gosec // see schedulerMetricsCAFileEnv doc comment.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

gitar-approved Added by Gitar

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants