Update CI setup and introduce CHANGELOG.md#70
Merged
Conversation
The pod validation failed in CI because of an Xcode-toolchain-related issue which more recent versions of CocoaPods address. ``` - NOTE | [iOS] xcodebuild: error: Cannot code sign because the target does not have an Info.plist file and one is not being generated automatically. Apply an Info.plist file to the target using the INFOPLIST_FILE build setting or generate one automatically by setting the GENERATE_INFOPLIST_FILE build setting to YES (recommended). (in target 'App' from project 'App') ```
crazytonyli
approved these changes
Oct 20, 2022
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
2 participants
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
CHANGELOG.mdsetup is based on wordpress-mobile/WordPressKit-iOS#545 and the PR template iteration from wordpress-mobile/WordPressUI-iOS#119.The CI upgrade is something I noticed because I don't have Ruby 2.6.4 (currently on
develop) on my main Apple Silicon machine, and I got an error about it from which followed the rest of the tooling upgrade.