fix(build): propagate packaged version through cluster artifacts#164
Merged
fix(build): propagate packaged version through cluster artifacts#164
Conversation
Closes #159 Pass the computed cargo version through Docker and cluster packaging paths so deployed clusters report the built artifact version while keeping latest and explicit version tags aligned.
Keep the runtime fix focused on Docker/server artifact versions and leave the bundled Helm chart path/version unchanged.
drew
pushed a commit
that referenced
this pull request
Mar 16, 2026
Pass the computed cargo version through Docker and cluster packaging paths so deployed clusters report the built artifact version while keeping latest and explicit version tags aligned.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #159
Summary
Propagate the computed Cargo/package version through Docker and cluster packaging paths so deployed clusters report the built artifact version instead of the workspace default.
Keep release publishing aligned by tagging published images with both
latestand the explicit version tag while preserving existing cache scope inputs.Changes Made
deploy/docker/Dockerfile.server,tasks/scripts/docker-build-component.sh: pass the computed Cargo version into server image builds, including local fallback builds.tasks/scripts/docker-build-cluster.sh,tasks/scripts/docker-publish-multiarch.sh: package the Helm chart with the computed version/appVersion and clear stale chart tarballs before packaging.deploy/kube/manifests/navigator-helmchart.yaml,deploy/docker/cluster-entrypoint.sh: replace the hardcoded chart filename with a runtime placeholder and resolve exactly one bundled chart at container start..github/workflows/docker-build.yml,.github/workflows/publish.yml: compute the cargo version in CI, propagate it into Docker builds, and publish explicit version tags alongsidelatest.architecture/build-containers.md: document runtime version propagation and dual-tag publishing.Deviations from Plan
None — implemented as planned.
Tests Added
navigator/server:devandnavigator/cluster:devwith synthetic/computed versions and verified the packaged chart filename and embedded server version changed accordingly.Documentation Updated
architecture/build-containers.md: documented version propagation for server and cluster artifacts plus dual-tag publishing.Verification