chore: release 0.22.0 — backfill CHANGELOG and bump version#128
Merged
Conversation
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.
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
oddkit | 2ea2008 | Commit Preview URL Branch Preview URL |
Apr 20 2026, 01:25 PM |
klappy
added a commit
that referenced
this pull request
Apr 20, 2026
Main shipped 0.22.0 via PR #128 while this branch was in Sonnet 4.6 validator dispatch. PR #128 backfilled CHANGELOG + version bump covering the envelope-conformance fixes from PR #124 (telemetry_public) and PR #125 (catalog generated_at). Per klappy://canon/constraints/release-validation-gate Rule 3 (canon outranks session artifacts), this refactor is re-versioned to 0.23.0. The handoff's "ship as 0.22.0" recommendation was session-scoped; main- reality is the canon. Resolution: - CHANGELOG.md: my encode D5+D9 content moves to a new [0.23.0] section above the existing [0.22.0] (telemetry + catalog); added a version- note blockquote explaining the bump. - package.json / workers/package.json / both lockfiles: 0.22.0 → 0.23.0. - workers/src/orchestrate.ts: auto-merged cleanly (catalog fix touched runCatalog, encode refactor touched discoverEncodingTypes + classifier call sites; zero overlap). - workers/test/canon-tool-envelope.smoke.mjs: auto-merged cleanly (additive on both sides). Verified: - tsc --noEmit clean - governance-parser.test.mjs 105/105 pass - CHANGELOG structure: [Unreleased] [0.23.0] [0.22.0] [0.21.1] [0.21.0]... - All conflict markers removed Sonnet 4.6 validator verdict (session sesn_011CaF5vqjgzN7Mw8s84qvK9, PASS on all 5 corroborations) remains valid for the encode refactor content — the rebase does not touch any matcher code or action behavior. A fresh-context validator re-dispatch will run before promotion per release-validation-gate Rule 2 out of canon-discipline caution.
klappy
added a commit
that referenced
this pull request
Apr 20, 2026
…23.0) (#126) Migrates oddkit_encode's trigger-word classifier from regex alternation to stemmed phrase-subset matching — the last regex matcher in the canon-parity sweep. Closes the sweep. Originally scoped as 0.22.0 per the P1.3.4 handoff. While this branch was in Sonnet 4.6 validator dispatch, PR #124 (telemetry envelope) and PR #125 (catalog envelope) landed on main and were released as 0.22.0 via PR #128. Per klappy://canon/constraints/release-validation-gate Rule 3 (canon outranks session artifacts), this refactor rebases forward and ships as 0.23.0. Bugbot disposition (Rule 1): - 259170a (first cut, flat stemmedTokens): completed/neutral, high-severity finding on multi-word vocab flattening → fix-forwarded via 113ba11 - 113ba11 (Cursor autofix stemmedPhrases): completed/neutral, low-severity dead-code finding on intersectsStems → fix-forwarded via e404fe0 - e404fe0: completed/success - eaa1234 (CHANGELOG + assertion 16): completed/success - d2acf91 (merge origin/main): Bugbot cancelled (new commit pushed before completion) - 8a0636b (stale-comment fix): completed/success — final head Sonnet 4.6 validator (Rule 2): agent_011CaF5vo8B5UpqtfZAmSeui, session sesn_011CaF5vqjgzN7Mw8s84qvK9 — verdict PASS on all 5 corroborations against eaa1234. Rebase and comment-fix commits on top are textual/version-only and do not touch matcher code. A fresh validator dispatch will run against the main→prod promotion PR per Rule 2. Refs: - Handoff: klappy://odd/handoffs/2026-04-20-p1-3-4-encode-canon-parity - Canon basis: klappy://canon/principles/cache-fetches-and-parses, klappy://canon/principles/vodka-architecture - Binding gate: klappy://canon/constraints/release-validation-gate Non-blocking carry-forward: P13 — Input-E fallback classification (inputs with no canon vocab intersection fall through to types[0] alphabetical = Constraint). Pre-existing behavior, flagged by validator, outside P1.3.4 scope.
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.
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
Backfills
[Unreleased]with a 0.22.0 entry covering the two envelope fixes that landed today, and bumps the version acrosspackage.json,workers/package.json, and both lockfiles. Pre-commit hook verified version sync and typecheck clean.Why
0.21.1 shipped earlier today (P1.3.3 fix-forward). Two envelope-conformance fixes have since landed on main:
telemetry_publicenvelope now carriesserver_time,assistant_text,debuglike every other tooloddkit_catalogdebug.generated_atis response time, newdebug.index_built_atfield preserves the cache-build timestampBoth add envelope fields consumers can rely on — MINOR bump, following the PR #112 precedent.
What shipped since 0.21.1
Per the CHANGELOG entry:
debug.index_built_aton catalog envelopedebug.generated_atstale cached timestamp (fix(catalog): debug.generated_at is response time, not cached index timestamp #125)Both bugs caught during v0.21.1 regression testing; each shipped through the full release-validation-gate (Bugbot + independent Sonnet 4.6 validator with GO verdict).
Files changed
package.json— version 0.21.1 → 0.22.0workers/package.json— version 0.21.1 → 0.22.0package-lock.json— version + root entryworkers/package-lock.json— version + root entryCHANGELOG.md— new 0.22.0 sectionSmoke path
No code changes; CHANGELOG + version labels only. Branch preview auto-deploys; smoke will run against preview before merge. The main → prod promotion PR follows after this merges.
Release-validation-gate
completedbefore merging.Note
Low Risk
Low risk: documentation and package metadata version bumps only; no runtime code paths are modified in this PR.
Overview
Cuts the
0.22.0release by backfillingCHANGELOG.mdwith notes for the recently-landed envelope fixes (addsoddkit_catalogdebug.index_built_at; fixestelemetry_publicenvelope completeness; aligns catalogdebug.generated_atsemantics).Bumps the version to
0.22.0acrosspackage.json,workers/package.json, and both lockfiles.Reviewed by Cursor Bugbot for commit 2ea2008. Bugbot is set up for automated code reviews on this repo. Configure here.