Repository navigation
v3.81.1: Reproducible agent package across checkouts - #22
Merged
Merged
Conversation
The 3.81.0 release build of agent 1.8.2 had the same files as the installed package but different bytes: modes followed the building checkout's umask, and git does not track the empty service/templates tree. Builds now drop go-w and always create that tree. Adopting a pre-3.81.0 package compares contents, not bytes, and keeps it unchanged. Co-Authored-By: Claude Opus 5.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
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.81.0 release workflow built agent 1.8.2 with the same files as the package already installed across the fleet, but different bytes. File modes came from the building checkout's umask, and the empty
opnsense/service/templates/tree is untracked by git.🤖 Generated with Claude Code