Upstream released v2.3.2. The patch series replayed from v2.2.0 with no
conflicts, and passed:
cargo fmt on the fork-owned cratescargo test -p infisical -p interpolate (including the fail-closed guard)cargo check -p komodo_core -p komodo_periphery
The lockfile was refreshed for this release and committed onto the branch.
Branch: tdd/rebase/v2.3.2
Compare: tdd/patches...tdd/rebase/v2.3.2
A clean rebase is not a deployment. Before promoting, follow
docs/tdd/MAINTENANCE.md, then build the image and re-run the canary checks in
docs/tdd/CANARY-2026-08-19.md -- both defects found so far were invisible to
the test suite and only appeared against a live Core.
Promoting:
git branch -f tdd/patches tdd/rebase/v2.3.2
git branch -f tdd/release/v2.3.2 tdd/rebase/v2.3.2
git push origin tdd/patches tdd/release/v2.3.2
Reported by the Upstream parity workflow. It does not open the PR itself:
the organization disallows GitHub Actions creating pull requests, which is a
deliberate control this workflow should not work around.
Upstream released
v2.3.2. The patch series replayed fromv2.2.0with noconflicts, and passed:
cargo fmton the fork-owned cratescargo test -p infisical -p interpolate(including the fail-closed guard)cargo check -p komodo_core -p komodo_peripheryThe lockfile was refreshed for this release and committed onto the branch.
Branch:
tdd/rebase/v2.3.2Compare: tdd/patches...tdd/rebase/v2.3.2
A clean rebase is not a deployment. Before promoting, follow
docs/tdd/MAINTENANCE.md, then build the image and re-run the canary checks indocs/tdd/CANARY-2026-08-19.md-- both defects found so far were invisible tothe test suite and only appeared against a live Core.
Promoting:
Reported by the Upstream parity workflow. It does not open the PR itself:
the organization disallows GitHub Actions creating pull requests, which is a
deliberate control this workflow should not work around.