Skip to content

chore(release): v0.1.26 - #543

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

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

Conversation

@dray92

@dray92 dray92 commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor

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

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

@gitar-bot

gitar-bot Bot commented Oct 22, 2026 •

Copy link
Copy Markdown
CI failed: The release PR's CI failed in two ways: the Kind CRD-adoption image preload step cannot find the digest-pinned kubectl image on the kind node (blocking the deploy and test steps in 4 jobs, related to the PR), and golangci-lint flagged overlong lines and prealloc issues in helm-chart test files (related-to-PR unclear).

Overview

There are 3 unique error templates across 5 logs. Two distinct failure patterns appear: a kind image-preload failure that blocks all downstream test steps (4 jobs, related to this PR), and a golangci-lint failure in Helm chart test files (relationship to the PR unclear). No flaky-test signal was found.

Failures

Kind CRD-adoption image not found by kubelet after preload (confidence: high)

  • Type: tooling
  • Affected jobs: 120159302695, 120159302682, 120159302691, 120159302748
  • Related to change: yes
  • Root cause: hack/kind-preload-images.sh imports public.ecr.aws/devzeroinc/kubectl@sha256:... into the kind control-plane node, but kubelet cannot find the image by that digest-qualified reference (the node lists an import-<date>@sha256:... reference instead). The downstream deploy, stress test, and validation steps are skipped as a consequence. The logs do not show whether the imported name, containerd namespace, or reference check is the specific mismatch.
  • Suggested fix: Make the preloaded image available on the kind node under the exact reference configured in helm-chart/zxporter .crdAdoption.image, either by loading a consistent tagged reference or by explicitly aliasing the imported image to the requested digest in the node's containerd store. Verify the exact reference before proceeding.

golangci-lint violations in Helm chart test files (confidence: high)

  • Type: tooling
  • Affected jobs: 120158055438
  • Related to change: unclear
  • Root cause: Lint reports lines in helm-chart/zxporter/chart_globals_test.go exceeding the 120-character limit (lll), and prealloc findings for names (line 26) and granted (line 88) in helm-chart/zxporter/chart_crd_adoption_test.go. The PR touches these test files, but the supplied context does not include the edits, so it cannot be confirmed that this PR introduced these violations.
  • Suggested fix: Wrap the overlong lines in chart_globals_test.go to fit within 120 characters. Preallocate names and granted in chart_crd_adoption_test.go with appropriate capacities, then rerun golangci-lint.

Summary

  • Change-related failures: 1 failure (kind image preload), affecting 4 jobs and blocking the remaining test steps.
  • Infrastructure/flaky failures: None identified.
  • Unclear relationship: 1 lint failure (golangci-lint) in helm-chart test files; the PR touches these files but the edits were not available to confirm causation.
  • Recommended action: Fix the kind image-preload reference handling first, since it blocks all integration test steps. Then resolve the lint violations in the two helm-chart test files and rerun CI.
Code Review ✅ Approved

🔴 High risk · New cluster-token resolution and persistence plus expanded Kubernetes RBAC could bind credentials to the wrong cluster or expose additional cluster resources.

Advances public main to the released v0.1.26 commit, which is already tagged, for browser convenience. 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-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 22, 2026
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.

1 participant