[6.1] URL compatibility and bug fixes #1200
Merged
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.
Explanation: Cherry-picking
URL
bug fixes that improve compatibility and stability, aligning the 6.1 behavior with what we expect moving forward.Scope: Impacts some
URL
andURLComponents
APIs that were found to cause bincompat issues in apps due to new behavior. Changes were made to be more compatible with usage that was previously allowed. See #1113 for more details. Other PRs are small follow-on fixes for crashes or unintended behavior as a result of #1103 and #1113.Original PRs: #1103, #1110, #1113, #1117, #1119, #1139
Risk: Low - restores previous behaviors or fixes crashes, well-tested on Darwin and swift-foundation
main
branch.Testing: Added unit tests, swift-ci, testing on Darwin, stable in
main
for 1-2 months.Reviewers: @jmschonfeld, @itingliu, @parkera
Resolves #958 and #962 for
release/6.1