Skip to content

promote: 0.22.0 to prod (version bump + CHANGELOG for #124, #125)#129

Merged
klappy merged 2 commits into
prodfrom
main
Apr 20, 2026
Merged

promote: 0.22.0 to prod (version bump + CHANGELOG for #124, #125)#129
klappy merged 2 commits into
prodfrom
main

Conversation

@klappy
Copy link
Copy Markdown
Owner

@klappy klappy commented Apr 20, 2026

What

Promotes the 0.22.0 release chore (PR #128) from main to prod. Two commits, CHANGELOG + version-field changes only. No worker code changes — the code fixes (#124 telemetry_public envelope, #125 catalog debug.generated_at) already landed on prod via PR #127 at 13:18:31Z.

Why now

Prod is currently running the #124 and #125 behaviors (verified via file content on the prod branch) but reports version 0.21.1. This promotion brings the version label into sync with the shipped behavior and backfills the CHANGELOG with the 0.22.0 entries.

Commits being promoted

  • 2ea2008f36chore: release 0.22.0 — backfill CHANGELOG, bump version
  • 6d05f763cfMerge pull request #128 from klappy/chore/release-0.22.0

Files changed

Pre-existing drift on root package-lock.json (was stuck at 0.18.0) was noted and corrected during PR #128.

Release-validation-gate compliance

Rule 1: PR #128 passed all 5 CI checks including Bugbot completed/success. ✅

Rule 2: This specific promotion PR changes CHANGELOG + version metadata only — per canon (§What Counts As 'Load-Bearing Surface'Not load-bearing): CHANGELOG-only PRs and dependency/lockfile bumps are listed as not triggering Rule 2. Fresh-context validator dispatch is still being performed per canon's "Ambiguous cases default to load-bearing. When in doubt, dispatch the validator" guidance.

Note on #127: The load-bearing content (#124 and #125 code changes) promoted via PR #127 had Sonnet 4.6 validator dispatch on the feature branches with GO verdicts, but the full P1.3.1 five-corroboration pattern was not performed against the promotion PR itself. The fresh validator on THIS PR will include a retroactive live-smoke of #124 (telemetry_public envelope) and #125 (catalog generated_at freshness + index_built_at presence) behaviors directly against prod to close that gap.

Rule 3: No session artifact recommends skipping any step. ✅

Smoke path after merge

  • Prod auto-deploys on merge
  • Live-verify prod reports oddkit_version → 0.22.0
  • Live-verify telemetry_public returns the full 5-field envelope (already on prod per file check, but validate post-promotion version-bump doesn't regress)
  • Live-verify oddkit_catalog returns debug.generated_at fresh + debug.index_built_at present

References


Note

Low Risk
Only release metadata changes (version fields and CHANGELOG.md) with no functional code modifications, so runtime risk is minimal.

Overview
Promotes release 0.22.0 by updating package.json/lockfiles (root and workers/) to report version 0.22.0.

Backfills CHANGELOG.md with a new 0.22.0 section documenting the already-landed fixes for telemetry_public envelope conformance and oddkit_catalog debug timestamp fields (generated_at vs new index_built_at).

Reviewed by Cursor Bugbot for commit 6d05f76. Bugbot is set up for automated code reviews on this repo. Configure here.

oddkit-agent and others added 2 commits April 20, 2026 13:25
Bumps version in package.json, workers/package.json, and both lockfiles.
Fills CHANGELOG [Unreleased] with 0.22.0 entries covering PR #124
(telemetry_public envelope conformance) and PR #125 (catalog
debug.generated_at response time + new index_built_at field).

MINOR bump: both fixes add envelope fields consumers can rely on.

Both bugs caught during the v0.21.1 regression test sweep. Pre-commit
hook verified version sync and typecheck pass.

No code or test changes in this PR — documentation + version only.
@cloudflare-workers-and-pages
Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
oddkit 6d05f76 Commit Preview URL

Branch Preview URL
Apr 20 2026, 01:32 PM

@klappy klappy merged commit f6fe412 into prod Apr 20, 2026
5 checks passed
klappy added a commit that referenced this pull request Apr 20, 2026
Promotes oddkit 0.23.0 to prod: the P1.3.4 encode canon-parity refactor. Closes the sweep — all three tools now use stemmed matching and have their in-process derivation caches removed per klappy://canon/principles/cache-fetches-and-parses.

Release validation gate (klappy://canon/constraints/release-validation-gate):

Rule 1 — Bugbot completed on all merged SHAs (feat PR #126): 259170a/neutral→fixed, 113ba11/neutral→fixed, e404fe0/success, eaa1234/success, 8a0636b/success; promotion head 7542cbb: success.

Rule 2 — Independent fresh-context validators:
- Feat validator: agent_011CaF5vo8B5UpqtfZAmSeui, session sesn_011CaF5vqjgzN7Mw8s84qvK9 against eaa1234 — PASS on all 5 corroborations
- Promotion validator: agent_011CaF9tvJgRXQ6F96MtN4iu, session sesn_011CaF9tx18Af3z1Fy9trwz8 against 7542cbb — PASS on all 5 corroborations, smoke 223/0 × 3

Rule 3 — handoff's 0.22.0 recommendation overridden by main-reality (PR #128/#129 shipped 0.22.0 envelope fixes while this was in validator dispatch); rebased forward to 0.23.0 per canon-outranks-session-artifacts.

Non-blocking carry-forward: P13 — parseUnstructuredInput fallback-to-types[0] behavior for inputs with no canon vocab intersection. Pre-existing, surfaced by both validators, outside P1.3.4 scope.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant