-
-
Notifications
You must be signed in to change notification settings - Fork 196
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
ios.SPMPackages sets version to upToNextMajorVersion instead of exactVersion #5822
Comments
I just refactored this bit to support semver ranges, will be published on Implemented in: ionic-team/trapeze@709173c Available for testing in |
Thank you @rigor789, I tested it and seems to be working fine. The above configuration produces now an 'Exact Version' rule which is what is needed. Do you have an estimate when will it be released? I guess, in 8.8.3 but is that expected soon? |
Thanks for testing! I can get that released in the next few days - though also feel free to use the next tag until then. |
Issue Description
When I include an SPM dependency in the
nativescript.config.ts
file, I expect that it pulls down the exact version that I provide. Instead it inserts the dependency into the Xcode project as 'Up to Next Major Version' instead of 'Exact Version'.When providing this:
I expect the project to be generated like this:
Instead it is generated like this:
If this is the desired default behaviour, please provide an option to define this as an exact version.
Reproduction
Set in
nativescript.config.ts
:The generated Xcode project will contain the dependency as described above and will pull down version 200.5.1 instead of 200.5.0.
Relevant log output (if applicable)
No response
Environment
Dependencies
Please accept these terms
The text was updated successfully, but these errors were encountered: