Conversation
Align the README, website landing page, App Store description, and App Store release notes with the 4.2 feature set. This keeps the repository release copy consistent with the App Store Connect 4.2 versions created for iOS, macOS, and tvOS.
everpcpc
force-pushed
the
codex/release-4-2-appstore
branch
2 times, most recently
from
3e6e283 to
ed566dd
Compare
everpcpc
changed the title
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.
Problem
Preparing the 4.2 release required the checked-in product copy and the App Store Connect metadata to describe the same feature set, while the project version also needed to move forward for post-release work.
Approach
Refresh the local release copy with the 4.2 feature set, sync that description and release notes to the new 4.2 App Store versions for iOS, macOS, and tvOS, then bump the Xcode marketing/build version after the release metadata commit.
Scope