fix(api): pin Package.resolved to flipcash2-client-protocol 0.2.0 - #684
Merged
Conversation
#672 moved `FlipcashAPI/Package.swift` to `exact: "0.2.0"` without the `Package.resolved` that goes with it, so the workspace still pinned 0.1.0. Local builds hide this — SwiftPM re-resolves and rewrites the file — but Xcode Cloud runs with automatic dependency resolution disabled and fails the archive: an out-of-date resolved file was detected at Code.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved, which is not allowed when automatic dependency resolution is disabled Deploy Flipcash #512 is the first Xcode Cloud build of main since #672, and it failed this way. Commit the resolution the pin implies.
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.
#672 moved
FlipcashAPI/Package.swifttoexact: "0.2.0"for flipcash2-client-protocol,but the workspace
Package.resolvedstill pins0.1.0.Local builds hide the mismatch — SwiftPM just re-resolves and rewrites the file,
which is why it shows up as a dirty working tree rather than a failure. Xcode
Cloud runs with automatic dependency resolution disabled, so it fails the archive
instead:
Deploy Flipcash #512 is the first Xcode Cloud build of
mainsince #672 landed,and it failed on both
ValidationStepandResolvePackageDependenciesStepwiththat error. The builds in between were release-branch builds on commits that
predate the pin.
This commits the resolution the pin already implies — the same file a local
build produces.