Skip to content

Bump zxporter image #270

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Tzvonimir merged 1 commit into from
Feb 3, 2026
Merged

Bump zxporter image #270

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion helm-chart/zxporter/values.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ namespace: devzero-zxporter
image:
repository: docker.io/devzeroinc/zxporter
pullPolicy: IfNotPresent
tag: "v0.0.51"
tag: "v0.0.61"
Comment on lines 13 to +16
Copy link

@coderabbitai coderabbitai bot Feb 3, 2026

Choose a reason for hiding this comment

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

⚠️ 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:

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.


# ZXPorter configuration
zxporter:
Expand Down