Record that v3.14.1 does reproduce from its tag - #94
Merged
Conversation
The v3.14.1 record says the published executable could not be rebuilt from its tag. It can. .NET 10.0.12 was installed on the checking machine shortly after the release, and a clean detached checkout republished to exactly the shipped bytes, 698e558f...1280f. The record above it is left as written. It was true when the release was made, and this file does not rewrite what it shipped as. What happened is smaller than that record implies. The reproduction ran against a machine one runtime patch behind the runner, and the right response was to install the patch and try again. Instead the gap was written up as a permanent limitation and the release shipped without evidence that was five minutes away. The appendix says that plainly, because a record that reports a false negative as a finding is worse than one that reports nothing. The pinning observation stands and is the part worth keeping: both workflows resolve dotnet-version "10.0.x", so this evidence depends on the checking machine holding the same patch and nothing reports the moment it does not. This time that produced a false negative. The same looseness could hide a real one. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
The v3.14.1 record says the published executable could not be rebuilt from its tag. It can.
.NET 10.0.12 was installed on the checking machine shortly after the release, and a clean detached checkout of the tag republished to exactly the shipped bytes:
So the link established at v3.13.0 is unbroken: every release since has been rebuilt from its tag.
The original record is left as written, per this file's rule against rewriting what a release shipped as. The appendix states plainly what happened: the check ran against a machine one runtime patch behind, and the right response was to install the patch and retry — not to write the gap into the permanent record and ship without evidence that was five minutes away.
The pinning observation stands. Both workflows resolve
dotnet-version: "10.0.x", so this evidence still depends on the checking machine holding the same patch, and nothing reports the moment it does not. This time that produced a false negative; the same looseness could hide a real one.🤖 Generated with Claude Code