Repository navigation
privacycommand: audit build commands and source provenance - #22
Merged
Merged
Conversation
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.
CI builds could be labeled local and shallow checkouts could lose version-tag recognition. The common generator now detects CI automatically, distinguishes numeric version tags from snapshots, and logs dirty/tagged state independently. Xcode logs each target's actual timestamp and channel; release binaries retain their existing repository redaction.
All app command sets are documented in docs/BUILD-PROVENANCE.md and expose just info alongside just archive. Existing build recipes share the displayed identity with xcodebuild, and Apple workflows fetch tag/history refs.
Shared Apple workflows pin the merged source/tag correction in privacykey/gh-workflows#17. Manual macOS releases test and build the exact requested tag.
Validation: four local regression suites pass for this app, including real clean/dirty/tagged/shallow/detached Git fixtures, CI/Archive channel selection, metadata preservation, Fastlane overrides and archive verification. Justfile parsing passes; workflow lint adds no diagnostics relative to main. Portfolio integration checks passed for paired OrgOrbari iOS/macOS app plists and Orbari macOS Archive. Lyrebird's required Swift build and 371 tests pass. Signed publication was not exercised by this audit.