Repository navigation
Use shared UTC build identity for ordinary Xcode archives - #21
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.
Product → Archive now captures one fresh
YYYY.MMDD.HHMMUTC build identity and prepares derived plists before Xcode processes and signs them. App and extension versions, build numbers and timestamps match; release archives redact repository identifiers. Marketing versions remain inConfig/Shared.xcconfigwith their existing values.just archiveregenerates an XcodeGen project where needed, uses the normal signing setup and verifies Organizer/app/extension metadata. Prior export flows remain available asarchive-exportwhere present. Legacy release epoch/commit-count generators are replaced where applicable. Adds regression CI and archive instructions.Validation: real unsigned Release archives with no version/build arguments passed for macOS, including the privileged helper and guest executable. Capture, metadata preservation, overrides, signing-plan and extension mismatch regression checks pass, along with project generation, release syntax and whitespace checks. Signed export, provisioning and App Store upload were not exercised.
Shared reference: https://github.com/AdamXweb/AdamXweb/pull/1
The guest staging phase now honors
CODE_SIGNING_ALLOWED=NO; signed builds retain hardened runtime signing.