Repository navigation
sync: re-pin candidate onto kagent-dev/kagent main@844ea06b — DO NOT MERGE (CI run for the force-push) - #64
Merged
Conversation
QuentinBisson
force-pushed
the
sync/20260922-844ea06b5
branch
5 times, most recently
from
September 22, 2026 17:07
68b2604 to
9276b46
Compare
QuentinBisson
force-pushed
the
giantswarm
branch
from
September 22, 2026 18:29
5df8ba3 to
9276b46
Compare
QuentinBisson
pushed a commit
that referenced
this pull request
Sep 22, 2026
| 2026-09-22 18:30 | `800015d` | `844ea06` (2026-09-22) | `5df8ba3` → `9276b46` | 89 + 3 own (the chart's `harness.compaction`, the pin annotation, the Substrate pin on the line's dev build `0.0.0-dev.giantswarm.2026-09-22.13-15-52.hb3137f0` of v0.2.0-beta4) | `3999b3b` fix(harness): re-read the continuation state from /data on every turn — superseded upstream (kagent-dev#2823, `42d3301`); `e66fb5a` `229ae56` `cc11cc9` `646e7fe` the context compaction cherry-picks — superseded upstream (kagent-dev#2790, `7471879`, on the Harness); `79d5300` `7485ebf` the controller metrics — merged upstream squashed (kagent-dev#2886, `844ea06`) | by hand — the sync ([#60](#60)) stopped on the continuation patch; the third step of the 2026-09-22 three-line move (agentgateway `main@08f4563b`, Substrate v0.2.0-beta4); the per-source git credential reshaped onto upstream kagent-dev#2868's gateway injection (kagent-dev#2899), upstream's new `nightly.yaml` publish and its three actions removed in the fork's CI commit; candidate [#64](#64), 35 checks green |
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.
Problem
giantswarmis pinned at upstreammain@800015de(2026-09-14); upstreammain@844ea06bcarries kagent-dev#2886 (our metrics), kagent-dev#2790 (compaction, on the Harness), kagent-dev#2823 and kagent-dev#2868 (Substrate v0.2.0-beta4).Change
The carried commits rebased onto
main@844ea06b; dropped as merged upstream: the continuation re-read, the four compaction commits, the two metrics commits. The Substrate pin moves to the line's dev build0.0.0-dev.giantswarm.2026-09-22.13-15-52.hb3137f0(v0.2.0-beta4) until1.1.0is tagged, the chart rendersharness.compactionunder the platform Harness, the pin annotation namesmain@844ea06.This pull request exists for
ci-ok/scan-okonly. It lands by--force-with-leaseontogiantswarm(FORK.md, Manual re-pin) and is never merged.