Skip to content

chore: retire the parity gate - #1

Merged
bmc08gt merged 2 commits into
mainfrom
chore/retire-parity-gate
Aug 25, 2026
Merged

chore: retire the parity gate#1
bmc08gt merged 2 commits into
mainfrom
chore/retire-parity-gate

Conversation

@bmc08gt

@bmc08gt bmc08gt commented Aug 25, 2026

Copy link
Copy Markdown
Collaborator

verify-parity.sh compared this repo's generated output against the copy each app generated for
itself. Both apps now consume this package instead of generating —
code-android-app#1325 and
code-ios-app#645 delete the vendored
protos and the codegen that fed them — so there is no second output left to compare against. The
script's own header said to delete it at this point.

Merge this after both consumer PRs land. Until they do, the gate still has something to
compare against and still works.

What replaces it

Nothing, for contract drift — that failure mode is gone by construction once there is one
generation point.

For generator drift the protection moves entirely to scripts/toolchain.env. grpc-swift-2
reaches the plugin through a floating from: requirement, so the Swift output moves on a
transitive release with no contract change; 2.2.1 and 2.3.0 each rewrote hundreds of lines that
way. The gate used to catch that incidentally. Now the pins are the only thing that does, and
the comment in that file says so instead of pointing at the deleted script.

README

The Status section was built around the gate and around "never published to a real registry, and
neither app depends on it on a branch" — both false since 0.1.0. It now records what the
comparison found, in the past tense, rather than promising it stays green.

verify-parity.sh compared this repo's generated output against the copy each app
generated for itself. Both apps now consume this package instead of generating —
code-android-app#1325 and code-ios-app#645 delete the vendored protos and the
codegen that fed them — so there is no second output left to compare against. The
script's own header said to delete it at this point.

What the gate was actually protecting is generator drift, and that protection moves
entirely to scripts/toolchain.env: grpc-swift-2 reaches the plugin through a floating
`from:` requirement, so the Swift moves on a transitive release with no contract
change and nothing downstream to catch it. Its comment says so directly now.

The READMEs' Status sections were written around the gate and around "never published,
no app depends on it," both of which stopped being true at 0.1.0. Rewritten to record
what the comparison found rather than to promise it stays green.
The consumer PRs merged, so the Status sections' "open, not merged" no longer holds.
Drops the "Not done yet" heading; the coordinates-vs-namespace note under it is a
standing fact, not an open item, so it keeps its own heading here.
@bmc08gt
bmc08gt merged commit 0cf7d83 into main Aug 25, 2026
2 checks passed
@bmc08gt
bmc08gt deleted the chore/retire-parity-gate branch August 25, 2026 16:28
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