Repository navigation
fix(kagent): re-pin the line to v0.11.0-gs.3 (the second automated re-pin, upstream 6a6b54ff) - #370
Merged
Merged
Conversation
Published Helm chart
|
| Chart | agent-platform |
| Version | 4.6.1-dev.kagent-repin-gs3.2026-09-11.07-59-03.ha3b2a31 |
| OCI reference | oci://gsoci.azurecr.io/charts/giantswarm/agent-platform:4.6.1-dev.kagent-repin-gs3.2026-09-11.07-59-03.ha3b2a31 |
| Digest | sha256:2dda411219d0fe15bdf61e9c3a07245840aaf05fd2ea02491bcae9b2273edf79 |
| Registry | public — gsoci.azurecr.io |
| Git catalog | giantswarm-test-catalog (index) |
Pull this chart
helm pull oci://gsoci.azurecr.io/charts/giantswarm/agent-platform --version 4.6.1-dev.kagent-repin-gs3.2026-09-11.07-59-03.ha3b2a31Posted by architect-orb · build 5724 · commit a3b2a31 · updated in place on every push
Published Helm chart
|
| Chart | agent-platform-connectivity |
| Version | 4.6.1-dev.kagent-repin-gs3.2026-09-11.07-59-03.ha3b2a31 |
| OCI reference | oci://gsoci.azurecr.io/charts/giantswarm/agent-platform-connectivity:4.6.1-dev.kagent-repin-gs3.2026-09-11.07-59-03.ha3b2a31 |
| Digest | sha256:7dccc9f2e0a599ebad302b67364291b318ec4cfc9c1fcf9ea65308b30878b619 |
| Registry | public — gsoci.azurecr.io |
| Git catalog | giantswarm-test-catalog (index) |
Pull this chart
helm pull oci://gsoci.azurecr.io/charts/giantswarm/agent-platform-connectivity --version 4.6.1-dev.kagent-repin-gs3.2026-09-11.07-59-03.ha3b2a31Posted by architect-orb · build 5725 · commit a3b2a31 · updated in place on every push
teemow
force-pushed
the
kagent-repin-gs3
branch
from
September 11, 2026 07:47
3e02117 to
a251f4d
Compare
…-pin, upstream 6a6b54ff) The line's second re-pin moved the consumed branch onto upstream kagent-dev/kagent main @ 6a6b54ff (kagent-dev/kagent#2786, #2785, #2797) with the 21 carried patches replayed clean. kagent.tag -> 0.11.0-gs.3, kagent.harness.image -> the gs.3 Go ADK index digest (meta and connectivity charts); the range >=0.11.0-gs.1 <0.11.1-0 is unchanged; examples/customer-bom.yaml and tests/verify-kagent-crds.py move with it. Lab-proven on the same tree (dev build hed07617): platform-test, agents-test, toolsets-test --skip-portal, skills-test green. Inert behind the fleet's <4.0.0 bound.
teemow
force-pushed
the
kagent-repin-gs3
branch
from
September 11, 2026 07:59
a251f4d to
a3b2a31
Compare
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
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.
What
Re-pin
components.kagent/components.kagent-crdsfromv0.11.0-gs.2tov0.11.0-gs.3(giantswarm/kagent-upstream, commited07617b):kagent.tag→0.11.0-gs.3(the controller and UI image build)kagent.harness.image→ thegs.3Go ADK index digestsha256:a2d23f5e…(meta chart and connectivity chart)examples/customer-bom.yamlandtests/verify-kagent-crds.py(KAGENT_LINE_REF) move with the pin; the generated READMEs are regenerated; CHANGELOG entry under UnreleasedThe range
>=0.11.0-gs.1 <0.11.1-0is unchanged. The GRPCRoute service list is unchanged too: nothing underproto/moved at the pin.Why
v0.11.0-gs.3is the head of the line's second automated re-pin (sync-upstream.yamlrun 34571612774, 2026-09-11): upstream pin4a91c27→6a6b54ff, bringing kagent-dev/kagent#2786 (the Go ADK exports a turn's spans before its terminal event leaves the process), #2785 (the chart disables controller metrics whenbindAddressis empty or0) and #2797 (the built-in tool server's URL uses thekagent-toolsnamespace); the 21 carried patches replayed clean, none dropped. The upstreamgo.modSubstrate replace is still v0.0.26 — the Substrate pins do not move with this PR.Lab verification (isolated agentlab, cluster
agentlab-repin2, agentlab v0.32.0)The tag re-publishes the tree of dev build
0.11.0-dev.giantswarm.2026-09-11.06-51-42.hed07617, which was rolled into a lab of its own through aplatform.valuesFilesoverlay —components.kagent/kagent-crdspinned to the build,kagent.tagthe build, both platform Harnesses on the build'sgolang-adkandclaude-harnessindex digests — then:platform-testagents-testtoolsets-test --skip-portalSendMessagethrough the edge on kagent mainskills-testThe release images are rebuilt from the same tree, so this PR pins the release digests (
builds.mdon the fork'sledgerbranch, verified withcrane digest).Offline:
make verify-meta verify-components verify-kagent-crds verify-kagent-harness verify-kagent-routegreen on this branch (verify-kagent-crdsvalidates against thegs.3CRDs).No installation acts — the release stays inert behind the fleet's
<4.0.0bound.Refs giantswarm/giantswarm#37010