Skip to content

[6.0] Enable -user-module-version for 6.0 #7606

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
May 29, 2024

Conversation

MaxDesiatov
Copy link
Contributor

@MaxDesiatov MaxDesiatov commented May 29, 2024

Cherry-pick of #7263.

Explanation: #if canImport(LibFoo, _version: "1.2.3") is not currently supported by SwiftPM, as this feature was gated on .vNext, even though it landed before SwiftPM 5.10 branched off.
Scope: Isolated to llbuild build manifests and packages that have 6.0 set as their tools version.
Risk: Low as covered with a test and gated to 6.0 tools version, so shouldn't impact existing packages.
Testing: Existing testPackageDependencySetsUserModuleVersion case updated to check for 6.0 version.
Issue: rdar://121124842
Reviewer: @bnbarham

@MaxDesiatov MaxDesiatov added build system Changes to interactions with build systems package manifests changes to package manifest APIs labels May 29, 2024
@MaxDesiatov
Copy link
Contributor Author

@swift-ci test

@bnbarham bnbarham merged commit eb3b9c6 into release/6.0 May 29, 2024
5 checks passed
@bnbarham bnbarham deleted the maxd/user-module-version-6.0 branch May 29, 2024 21:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug build system Changes to interactions with build systems package manifests changes to package manifest APIs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants