Add unsafe flags policy change to changelog#10180
Open
ole wants to merge 1 commit into
Open
Conversation
I learned about this change by chance through an unrelated discussion (<swiftlang/swift-evolution#3290 (comment)>). I think it’s a big enough change to warrant inclusion in the changelog, especially because it invalidates part of an accepted Swift Evolution proposal.
ole
requested review from
bkhouri,
bripeticca,
cmcgee1024,
daveinglis,
daveyc123,
dschaefer2,
jakepetroules,
owenv,
plemarquand and
rconnell9
as code owners
June 8, 2026 13:14
Contributor
Author
|
cc @dschaefer2 |
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.
Adds information to the changelog about the policy change how SwiftPM handles dependencies with unsafe flags since Swift 6.2.
Motivation:
I learned about this change by chance through an unrelated discussion (swiftlang/swift-evolution#3290 (comment)). I think it’s a big enough change to warrant inclusion in the changelog, especially because it invalidates part of an accepted Swift Evolution proposal.
Modifications:
Added an entry to the top of the changelog for Swift 6.2.
Result:
No change to the code or functionality.