Problem
The vanity-gateway Helm chart at deploy/helm/vanity-gateway is not registered
in tools/ci/github-release-subprojects.json. Release automation derives a
subproject's tag format from that registry, so no
deploy/helm/vanity-gateway/v<X.Y.Z> tag is ever cut and no chart version can
be released or published.
Every other published chart under deploy/helm has an entry. This one does
not. The service lane at src/invocation-plane-services/vanity-gateway is
registered and has released through v1.32.1, so only the chart is affected.
Additional detail
deploy/helm/vanity-gateway/helm-nvcf-vanity-gateway/Chart.yaml still carries
version: 0.1.0-nvcf-10204.1, the version of the published artifact the chart
was recovered from in #873. That is not a form the release tooling accepts.
The subtree docs are also stale. AGENTS.md and README.md state that no
release lane is registered, and AGENTS.md reports an appVersion of
1.25.0-nvcf-10204.0 while Chart.yaml has carried 1.32.1 since the import.
Expected
The chart is registered like its siblings so the path-format release tag is
produced, the version line is seeded above the recovered 0.1.0-nvcf-10204.x
artifacts, the committed chart version follows the repo convention for
pipeline-versioned charts, and the subtree docs match the code.
Problem
The vanity-gateway Helm chart at
deploy/helm/vanity-gatewayis not registeredin
tools/ci/github-release-subprojects.json. Release automation derives asubproject's tag format from that registry, so no
deploy/helm/vanity-gateway/v<X.Y.Z>tag is ever cut and no chart version canbe released or published.
Every other published chart under
deploy/helmhas an entry. This one doesnot. The service lane at
src/invocation-plane-services/vanity-gatewayisregistered and has released through
v1.32.1, so only the chart is affected.Additional detail
deploy/helm/vanity-gateway/helm-nvcf-vanity-gateway/Chart.yamlstill carriesversion: 0.1.0-nvcf-10204.1, the version of the published artifact the chartwas recovered from in #873. That is not a form the release tooling accepts.
The subtree docs are also stale.
AGENTS.mdandREADME.mdstate that norelease lane is registered, and
AGENTS.mdreports anappVersionof1.25.0-nvcf-10204.0whileChart.yamlhas carried1.32.1since the import.Expected
The chart is registered like its siblings so the path-format release tag is
produced, the version line is seeded above the recovered
0.1.0-nvcf-10204.xartifacts, the committed chart version follows the repo convention for
pipeline-versioned charts, and the subtree docs match the code.