You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
% swift --version
Apple Swift version 4.0 (swiftlang-900.0.43 clang-900.0.22.8)
Target: x86_64-apple-macosx10.9
% xcodebuild -version
Xcode 9.0
Build version 9M136h
Additional Detail from JIRA
Votes
0
Component/s
Package Manager
Labels
Bug
Assignee
None
Priority
Medium
md5: defa6f030912516014d658ed48822ec9
duplicates:
SR-1039 Fetch a dependency with a specified Pre-release version
Issue Description:
When using from: "major.minor.patch" to specify a version constraint, the package manager incorrectly resolves prerelease tags from the next major version as compatible with the current major version.
To avoid surprises, I feel like swiftpm shouldn't consider prerelease versions unless you explicitly opt into them on a dependency-by-dependency basis in the manifest.
Environment
% swift --version
Apple Swift version 4.0 (swiftlang-900.0.43 clang-900.0.22.8)
Target: x86_64-apple-macosx10.9
% xcodebuild -version
Xcode 9.0
Build version 9M136h
Additional Detail from JIRA
md5: defa6f030912516014d658ed48822ec9
duplicates:
Issue Description:
When using
from: "major.minor.patch"
to specify a version constraint, the package manager incorrectly resolves prerelease tags from the next major version as compatible with the current major version.Sample project: https://github.com/sharplet/swiftpm-prerelease-bug
The text was updated successfully, but these errors were encountered: