Prepare for 6.0.0 release - #285
Closed
w-goog wants to merge 2 commits into
Closed
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.
Release prep for GTMAppAuth 6.0.0.
CHANGELOG
#280(BREAKING) AppAuth 3.0.0, deployment target andswift-tools-versionbumps.#284GTMSessionFetcher widened to 4.x and 5.x, closing The gtm-session-fetcher dependency is locked to an old version #273, plus the CocoaPods dev dependency#267Swift 6Sendableconformances in the keychain store, which had no entry at all#278UIScene lifecycle migration in the iOS example#279xcconfig-based client configuration in the iOS example, which had no entry at allThe CI-only PRs (#266, #274, #282) are deliberately left out as not user-facing.