Repository navigation
feat: show which contract packages the build carries - #1476
Merged
Merged
Conversation
github-actions
Bot
added
type: feature
bmc08gt
force-pushed
the
feat/contract-info-surfacing
branch
from
September 16, 2026 21:37
e1cde6e to
3852ed9
Compare
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
1 participant
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.
A build in someone's hand does not say which backend contract it speaks. The pinned
versions are in
libs.versions.toml, but the upstream proto commit each one was generatedfrom is not in this repo at all, and a build running on
protoLocalRootlooks identical toa published one.
Both contract packages now carry that metadata themselves (ocp 0.5.0, flipcash2 0.9.0), so
this reads it rather than deriving it. Two surfaces:
Labs, under Developer, next to the existing staff-gated rows — one row per package showing
<version> · <short proto commit>. A package built from a local proto sync reportsLOCALinstead of a SHA and the row turns
warning, so it stands out on a screenshot.The exported log header, which already carries app version, device and build, gains
OCP Contract:andFC2 Contract:lines in the same shape. That is the surface thatmatters on a bug report, where nobody can go and look at the screen.
:libs:loggingpicks up a compile dependency on both packages. They are already in the appgraph through
:services:opencodeand:services:flipcashand both ship their own keeprules, so the APK is unchanged.