Records/golang/go.yaml.in/yaml/v2/failure issue

Where it was measured

PASS means the release recorded a passing observation at PROJECT_COMPILE and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.

• v2.4.4 FAIL
• v2.4.3 not measured
• v2.4.2 not measured

Where it reproduced

• os=linux · runtime=go@1.26 ×2 2026-08-31 → 2026-08-31

Nearest known PASS/FAIL boundaries

No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.

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.

Moved: 0 · unchanged at every release: 1

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.

Evidence gaps

• No release in this window recorded a passing observation at PROJECT_COMPILE.
• Releases in this window never measured at PROJECT_COMPILE: 2
• No failure domain was inferred for this failure.

Published answers for the affected releases

• go.yaml.in/yaml/v2 v2.4.4: Marshal Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWgo.yaml.in/yaml/v2.Marshal MIT-0 · 2026-09-06
• go.yaml.in/yaml/v2 v2.4.4: yaml.Marshal, yaml.Unmarshal Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWyaml.Marshalyaml.Unmarshal MIT-0 · 2026-08-28