Widen the swift-syntax range to allow 602 through 604 - #395
Merged
Conversation
`from: "601.0.0"` is up-to-next-major, which resolves to 601.0.0..<602.0.0 and pins every consumer to the 601 line. Consumers that need a newer swift-syntax -- for example a host app substituting a prebuilt 603 distribution -- cannot resolve at all, and there is no workflow-swift release they can move to. Widen it to 601.0.0..<605.0.0, matching what swift-macro-testing, swift-case-paths, swift-perception, and the rest of the Point-Free packages already declare. Also move the Tuist sample's resolved pins to swift-syntax 603.0.2 so the sample actually exercises the newly allowed range rather than staying on 601. That requires bumping swift-perception alongside it: 2.0.6 caps swift-syntax at `509..<602`, and 2.0.11 widens it to `509..<605`. The root manifest already allows `1.5.0..<3.0.0`, so no manifest change is needed for that bump. WorkflowSwiftUIMacros builds against swift-syntax 603.0.2 and all 13 ObservableStateMacro expansion tests pass with byte-identical output, so no source change is needed alongside the range bump. 603 does deprecate the `MemberMacro` `expansion(of:providingMembersOf:in:)` overload in favour of the `conformingTo:` variant; that is a warning only, and adopting it is left to a separate change. Co-authored-by: Claude Code <noreply@anthropic.com> Ai-assisted: true
|
|
johnnewman-square
approved these changes
Aug 25, 2026
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
3 participants
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.
Issue
from: "601.0.0"is up-to-next-major, which resolves to 601.0.0..<602.0.0 and pins every consumer to the 601 line. Consumers that need a newer swift-syntax -- for example a host app substituting a prebuilt 603 distribution -- cannot resolve at all, and there is no workflow-swift release they can move to.Fix
Widen it to 601.0.0..<605.0.0, matching what swift-macro-testing, swift-case-paths, swift-perception, and the rest of the Point-Free packages already declare.
Checklist