Recordsgolanggoogle.golang.org/protobufv1.36.5google.golang.org/protobuf/proto.Marshal
Change the conditions
Current conditions
google.golang.org/protobuf/proto.Marshal @v1.36.5ubuntu glibc · x64 · go 1.26 · go 1
1 of 1 passed
Observed — real project builds reported from this coordinate.
no sample at this coordinate yet
- Project observations
- 1 / 1
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-08-31
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v1.36.5
linux · go@1.26
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:2a77dcac85612836e905e431d580018ebe2264f265f4cf4360f701ed9c9d2809
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/golang/protobuf | v1.5.4 | CANDIDATE Correlated change; unproven combination | contract passed | 10 project-days |
| github.com/google/go-cmp | v0.6.0 | CANDIDATE Correlated change; unproven combination | nothing measured | 3 project-days |
| github.com/google/go-cmp | v0.7.0 | CANDIDATE Correlated change; unproven combination | contract passed | 7 project-days |
The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
| Library | v1.36.12 | v1.36.11 | v1.36.10 | v1.36.6 | v1.36.5 | v1.34.2 | v1.33.0 | v1.32.0 | v1.28.0 | v1.26.0 | v1.26.0-rc.1 | v1.23.0 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| github.com/golang/protobuf | v1.5.2 | v1.5.0 | v1.5.0 | v1.5.0 | v1.5.4 | v1.5.0 | v1.5.4 | v1.5.0 | v1.5.0 | v1.5.3 | — | v1.4.3 |
| github.com/google/go-cmp | v0.7.0 | v0.7.0 | v0.7.0 | v0.5.5 | v0.6.0 | v0.5.5 | v0.5.5 | v0.5.5 | v0.5.5 | v0.5.5 | v0.5.5 | v0.4.0 |
Moved: 2 · unchanged at every release: 0
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.
Recent failure clusters
-
observed UNKNOWN exit 1 Evidence gap ×1 v1.36.5 os=linux · runtime=go@1.26 sha256:2a77dcac8561…Contract test failed: expected error when ExportSpans is called on unstarted exporter, got nil · exit status 1go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01Diagnostic re-verification candidate
-
observed PROJECT_COMPILE exit 1 ×1 v1.36.5 os=linux · runtime=go@1.26 sha256:e84876b56a4e…test/contract.go:<n>:<n>: assignment mismatch: 1 variable but otlptrace.New returns 2 values …go/compiler · compiler-diagnostic · outer go runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-02 · Last seen: 2026-09-02
-
observed PROJECT_TEST exit 1 ×1 v1.36.5 os=linux · runtime=go@1.26 sha256:4d9975558e16…--- FAIL: TestWithoutInsecureFailsPlaintext (10.00s) · FAIL example.com/otlptracegrpc-insecure/test 10.009sgo/test · test-runner-diagnostic · outer go testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-02 · Last seen: 2026-09-02
-
observed PROJECT_TEST exit 1 ×1 v1.36.5 os=linux · runtime=go@1.26 sha256:b6b84f5f81cf…--- FAIL: TestWithInsecureContract (10.00s) · contract_test.go:<n>: expected at least one gRPC trace export request, got none …go/test · test-runner-diagnostic · outer go testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-02 · Last seen: 2026-09-02