[6.2] Guard unsafeFlags with Windows-only conditional to restore SwiftPM compatibility #241
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
|
@swift-ci Please test |
franklinsch
approved these changes
Sep 17, 2025
This was referenced Sep 25, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is a cherry pick to the 6.2-aligned release branch, in preparation of a cherry-pick to
swift-markdown-0.7for a0.7.1release tag.unsafeFlagsin Package.swift to only Windows, so that tagged semver releases can still be made.0.7.0release tag was unusable on non-Windows platforms due to the use ofunsafeFlags.unsafeFlagsintroduced in Markdown 0.7.0 causes SwiftPM dependency resolution failures #239