Skip to content

chore(alloy): bump v1.19.2 → v1.20.1 (#183) - #185

Merged
procoduck merged 1 commit into
mainfrom
chore/alloy-v1.20.1
Sep 29, 2026
Merged

chore(alloy): bump v1.19.2 → v1.20.1 (#183)#185
procoduck merged 1 commit into
mainfrom
chore/alloy-v1.20.1

Conversation

@procoduck

@procoduck procoduck commented Sep 29, 2026

Copy link
Copy Markdown
Owner

Closes #183.

Draft until the proofs that aren't required checks are green:

  • e2e-k8s: the real receiver Alloy and G10's k8s-monitoring collectors. It runs automatically because versions.env and the Dockerfiles changed.
  • The compose E2E: real v1.20.1 agents register, poll and report APPLIED, and Stage 2 validates with the v1.20.1 binary. It's path-filtered off PRs, so I dispatch it on this branch.

What moves

  • The image pin, by digest: versions.env, the four Dockerfile* ARG defaults, and the compose fallbacks. check-docker is OK.
  • make schema → alloy-v1.20.1.json (186 components). The older artifacts stay embedded, as v1.18.1's already does.
  • Overlay:
    • _meta → v1.20.1.
    • Two new experimental components, otelcol.encoding.jsonlog and otelcol.encoding.text. They have no ports, no secrets and no network access, so they get category config and sim_secret_source: drop_ref, like the other otelcol extensions.
    • The reconcile tool rewrites the whole file (escaped Unicode, reordered keys). I discarded that in favour of a minimal edit.
  • Stated censuses: these tests exist so that anything moving here is recorded deliberately.
    • Dispositions: sim_secret_source 14 → 16.
    • Attribute paths: 6624 → 6705, with per-type counts including secret 337 → 338; credential-named 715 → 718 (519 not typed secret).
    • Address sweep: 674 → 675 paths probed. It still surfaces the same five relabel destinations and no new ones.
    • Rule K canary sweep: 4779 paths, with 612 reaching the sandbox (was 608). The four new sandbox-reaching paths are otelcol.processor.memory_limiter's {min,max}_gc_interval_when_{soft,hard}_limited, durations inside its measured-clean keep_subtree. Every other new path is dropped by the existing keep lists: receiver keepalive timeouts, exporter client.keepalive.*, the new auth capsules on tcplog/syslog, remote_write's sigv4.session_name, and cloudflare's max_request_body_size.
  • The visual corpus was regenerated; only the header version changed.
  • Docs pins (README, requirements page, spec, AGENTS image table) and the B1 — APPLIED status can mean 'polled', not 'loaded OK' #115 reproduction note now say v1.20.1.
  • CHANGELOG: filelog's top_n = 0 behaviour change.

Checks run locally

make schema-verify passes (every component resolves to exactly one S3 disposition). make test passes, including the simulate suite at 87/87. make lint is clean with docs drift OK, and make web-ci passes (644 tests).

🤖 Generated with Claude Code

https://claude.ai/code/session_01BPMsuQQBnedAsJ8tJMH3rw

Andre Staats @claude
chore(alloy): bump v1.19.2 → v1.20.1 (#183)
0d7a742 
Image pin (versions.env, the four Dockerfile ARG defaults, the compose
fallbacks) and ALLOY_VERSION move to v1.20.1 by digest; `make schema`
generated internal/schema/artifacts/alloy-v1.20.1.json (the v1.18.1 and
v1.19.2 artifacts stay, as before). Overlay: _meta to v1.20.1, and the two
new components — otelcol.encoding.jsonlog / .text, experimental, port-less
and secret-free — get category config and sim_secret_source drop_ref like
the other otelcol extensions. The reconcile tool's whole-file rewrite
(escaped unicode, reordered keys) was discarded for a minimal edit.

Stated censuses updated with what moved: dispositions (sim_secret_source
14 -> 16), attribute paths 6624 -> 6705 and the per-type/credential-name
counts, the address sweep (674 -> 675 paths, same five relabel
destinations), and rule K's canary sweep (4779 paths; the four new
sandbox-reaching ones are memory_limiter's GC-interval durations inside
its measured-clean keep_subtree — every other new path is dropped).
Visual corpus regenerated (header version only). Docs pins and the #115
reproduction note moved to v1.20.1; CHANGELOG notes filelog's top_n=0
behaviour change.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BPMsuQQBnedAsJ8tJMH3rw
@procoduck
procoduck marked this pull request as ready for review September 29, 2026 14:57
@procoduck
procoduck merged commit 9481748 into main Sep 29, 2026
27 checks passed
@procoduck
procoduck deleted the chore/alloy-v1.20.1 branch September 29, 2026 14:57
@procoduck procoduck mentioned this pull request Sep 30, 2026
Merged
procoduck added a commit that referenced this pull request Sep 30, 2026
@procoduck Andre Staats @claude
fix(ci): web jobs re-run when the schema, corpus or spec they read ch…
c2c6d77 
…anges (#190)

Two mocked specs hard-coded alloy-v1.19.2 as the "current" schema, but the
fixture loads the newest artifact on disk — v1.20.1 since #185 — so
"a visual pipeline rendered under an older schema is badged" found two
badges, and the unsaved-guard graph loaded as a schema upgrade. Both now
derive the version from the fixture (currentSchemaVersion).

Nothing caught it on #185 or on main's push because ci.yml's frontend gate
claimed nothing outside web/ affects web or test-ui. The web tests read
internal/schema/artifacts/ (schema fixture, l1 and wireOrient vitests),
internal/visual/testdata/corpus/ (renderTS.test) and docs/spec.md §12
(routeCoverage.test); all three now open the gate, spec.md kept past the
Markdown filter via a frontend_files list. repocheck requires each path
(red-checked against the old pattern) and the docs-only spec understands
the filtered list. Full mocked suite: 319 passed.


Claude-Session: https://claude.ai/code/session_01BPMsuQQBnedAsJ8tJMH3rw

Co-authored-by: Andre Staats <staats.andre@gmail.com>
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@procoduck procoduck mentioned this pull request Sep 30, 2026
Merged
procoduck added a commit that referenced this pull request Sep 30, 2026
@procoduck Andre Staats @claude
docs: housekeeping after v0.12.0 — ledger, gateway plan, kind plan (#193
30f9a92 
)

project-status: the document map's docs/plans row (now empty) and
gateway-plan row (all workstreams shipped, every gate signed); §3's
"done, unreleased" gateway and attribute-matching entries collapse to one
line now that they shipped in v0.12.0; §4 checks off the receiver tier and
dates W7/W9; the grpc hold now points at the Dependabot ignore (#187); a
new "On main, unreleased (next: v0.13.0)" section lists #185, #186, #192,
the dependency rounds and the CI gate fix.

gateway-tier-plan: header rewritten for all-shipped/all-signed; §9 rows
for W4/W7/W9 (shipped v0.12.0) and the stale W6 "gated" (v0.11.0), W10
"awaiting the SA UI" (v0.9.0) and W11 "rate limit still to build" (v0.9.0);
§11 decisions 6 and 7 (W9 publish target / ownership) marked resolved by
#112's design.

kind-test-environment-plan: the suite is twelve features, not nine.


Claude-Session: https://claude.ai/code/session_01BPMsuQQBnedAsJ8tJMH3rw

Co-authored-by: Andre Staats <staats.andre@gmail.com>
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@procoduck procoduck mentioned this pull request Sep 30, 2026
Merged
procoduck added a commit that referenced this pull request Sep 30, 2026
@procoduck Andre Staats @claude
chore(release): v0.13.0 / chart 0.17.0 (#194)
0652e9d 
Chart 0.17.0, appVersion 0.13.0. Ships Alloy v1.20.1 (#185), the
rejected-config status fix (#186, migration 0028), the two-replica
tenant-route apply fix (#192), plus the dependency rounds and CI gate
fix. Docs pins (README, scripts/docs-content, site/index.html eyebrow and
pill) bumped and site/docs regenerated; CHANGELOG Unreleased becomes
v0.13.0 with a summary and upgrade note; internal/spa/dist rebuilt.
No chart-values change, so no UPGRADING.md section.


Claude-Session: https://claude.ai/code/session_01BPMsuQQBnedAsJ8tJMH3rw

Co-authored-by: Andre Staats <staats.andre@gmail.com>
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@procoduck procoduck mentioned this pull request Oct 26, 2026
Merged
procoduck added a commit that referenced this pull request Oct 26, 2026
@procoduck Andre Staats @claude
chore(alloy): bump v1.20.1 -> v1.21.2 (#404)
cf235a6 
Image pin (versions.env by multi-arch index digest, the four Dockerfile ARG
defaults, the compose fallbacks; dev/kind takes it via __ALLOY_IMAGE__) and
ALLOY_VERSION move to v1.21.2; `make schema` generated
internal/schema/artifacts/alloy-v1.21.2.json and alloy_gen.go (the v1.18.1,
v1.19.2 and v1.20.1 artifacts stay). Overlay: _meta to v1.21.2 and the removed
prometheus.exporter.catchpoint dropped, as a minimal edit (the reconcile
tool's whole-file rewrite was discarded, as in #185).

Stated censuses updated with what moved: sim_keep 90 -> 89 (catchpoint);
attribute paths 6705 -> 6785 and the per-type counts; upstream #7499 retyped
59 credential-named paths string -> secret (credential-named-not-secret
519 -> 460); rule K's canary sweep 4779 -> 4840 paths with present unchanged
at 612 (no new path reaches the sandbox); the address sweep 675 -> 681 with
the same relabel-destination leak set and rendered count. wizardtest's
runtimeErrors strings re-confirmed verbatim against v1.21.2 and the pin moved.
Visual corpus regenerated (header version only). Docs pins moved; CHANGELOG
notes the v1.21 pipeline behaviour changes.


Claude-Session: https://claude.ai/code/session_01Qq4QJuHU7jTnR9ZtWvjDdu

Co-authored-by: Andre Staats <staats.andre@gmail.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Bump Alloy v1.19.2 → v1.20.1 (schema bump)

1 participant

@procoduck