Bump zxporter image

[Tzvonimir]

[Title]

📚 Description of Changes

Provide an overview of your changes and why they’re needed. Link to any related issues (e.g., "Fixes #123"). If your PR fixes a bug, resolves a feature request, or updates documentation, please explain how.

• What Changed:
  (Describe the modifications, additions, or removals.)

• Why This Change:
  (Explain the problem this PR addresses or the improvement it provides.)

• Affected Components:
  (Which component does this change affect? - put x for all components)

• Compose

• K8s

• Other (please specify)

❓ Motivation and Context

Why is this change required? What problem does it solve?

• Context:
  (Provide background information or link to related discussions/issues.)

• Relevant Tasks/Issues:
  (e.g., Fixes: #GitHub Issue)

🔍 Types of Changes

Indicate which type of changes your code introduces (check all that apply):

• BUGFIX: Non-breaking fix for an issue.
• NEW FEATURE: Non-breaking addition of functionality.
• BREAKING CHANGE: Fix or feature that causes existing functionality to not work as expected.
• ENHANCEMENT: Improvement to existing functionality.
• CHORE: Changes that do not affect production (e.g., documentation, build tooling, CI).

🔬 QA / Verification Steps

Describe the steps a reviewer should take to verify your changes:

1. (Step one: e.g., "Run make test to verify all tests pass.")
2. (Step two: e.g., "Deploy to a Kind cluster with make create-kind && make deploy.")
3. (Additional steps as needed.)

✅ Global Checklist

Please check all boxes that apply:

• I have read and followed the CONTRIBUTING guidelines.
• My code follows the code style of this project.
• I have updated the documentation as needed.
• I have added tests that cover my changes.
• All new and existing tests have passed locally.
• I have run this code in a local environment to verify functionality.
• I have considered the security implications of this change.

Summary by CodeRabbit

• Chores
  • Updated the default container image tag to v0.0.61 in the Helm chart values.
  • New installs and upgrades will automatically deploy the newer application image.
  • No changes to chart templates or configuration keys; behavior remains consistent aside from the updated image version.

[coderabbitai]

📝 Walkthrough

Walkthrough

Updates the Helm chart values for zxporter by changing the container image tag from v0.0.51 to v0.0.61. No other files or configurations are modified.

Changes

Cohort / File(s)	Summary
Helm chart version bump helm-chart/zxporter/values.yaml	Update container image tag from v0.0.51 to v0.0.61.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Bump image version in helm chart #209: Also bumps zxporter image tag in the same values.yaml file.
• Update default zxporter values image #202: Updates the same helm-chart/zxporter/values.yaml image tag to a different version.
• Bump zxporter image to 0.0.51 #218: Modifies the same Helm values file to adjust the zxporter image version.

Suggested reviewers

• Parthiba-Hazra
• dray92

Poem

I twitch my whiskers—versions hop anew,
From .51 to .61, a chart in view.
In YAML burrows, tags align,
A tidy bump, deployment fine.
Carrot logs show green and bright—
Ship the pod, then nibble night. 🥕🐇

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Linked Issues check	⚠️ Warning	The change only bumps the image tag and does not address the 'cluster snapshot enum name fix' required by issue #123.	Implement the enum name fix for cluster snapshots as specified in issue #123 or remove the link to that issue.
Out of Scope Changes check	⚠️ Warning	Bumping the image tag is unrelated to the linked issue #123 about fixing the cluster snapshot enum name.	Remove the unrelated image bump or include only changes relevant to issue #123.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change of updating the zxporter image version.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch tzvonimir/bump-zxporter-image

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@helm-chart/zxporter/values.yaml`:
- Around line 13-16: Confirm compatibility for image tag referenced under
image.repository (docker.io/devzeroinc/zxporter) and image.tag ("v0.0.61") by
locating the underlying Git commit or inspecting the image metadata; run docker
image inspect devzeroinc/zxporter:v0.0.61 (or pull and inspect the image labels)
to identify breaking changes, record the commit SHA or label details, and either
add a changelog entry describing any relevant changes or update values.yaml to a
vetted, documented tag.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🌐 Web query:

devzeroinc zxporter v0.0.61 docker tag release notes changelog

💡 Result:

I couldn’t find any public release notes / changelog specifically for the devzeroinc/zxporter:v0.0.61 Docker tag (e.g., no GitHub “Releases” entry or docs page that lists changes per zxporter image tag).

What DevZero does publish publicly is operational docs (install/update + registry info), including:

• Update command that applies the latest installer manifest from the zxporter repo (dist/installer_updater.yaml). [1]
• Note that zxporter images are hosted on Docker Hub under devzeroinc and mirrored to public.ecr.aws/devzeroinc with consistent tags. [1]

Practical workaround to derive “what changed” for v0.0.61:

• Compare the Git commit/tag behind v0.0.61 to the previous tag in the zxporter GitHub repo (if tags are visible), or
• Pull both images and compare image digests/labels and/or run a filesystem diff:
  • docker pull devzeroinc/zxporter:v0.0.61
  • docker image inspect devzeroinc/zxporter:v0.0.61 (check labels like revision/commit, build date, etc.)

If you want, tell me what you consider the “previous” tag (or paste docker image inspect output for v0.0.61), and I can help you reconstruct a changelog-style diff.

References:
[1] DevZero docs – zxporter troubleshooting / update + registry note (devzero.io)

Citations:

• 1: https://www.devzero.io/docs/k8s-automation/troubleshooting/overview?utm_source=openai

---

Verify compatibility for image tag v0.0.61

• No public changelog exists for v0.0.61; verify the underlying Git commit or inspect image labels (docker image inspect devzeroinc/zxporter:v0.0.61) for breaking changes or include a changelog entry.

🤖 Prompt for AI Agents

In `@helm-chart/zxporter/values.yaml` around lines 13 - 16, Confirm compatibility
for image tag referenced under image.repository (docker.io/devzeroinc/zxporter)
and image.tag ("v0.0.61") by locating the underlying Git commit or inspecting
the image metadata; run docker image inspect devzeroinc/zxporter:v0.0.61 (or
pull and inspect the image labels) to identify breaking changes, record the
commit SHA or label details, and either add a changelog entry describing any
relevant changes or update values.yaml to a vetted, documented tag.