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
I am new to Sources and setting up using SPM command plugin.
In the Package.swift file .package(url: "https://github.com/krzysztofzablocki/Sourcery.git", revision: "3a9e5f1014ac09b30727c01d2a0e1531dac30948") (use commit of 1.9.2 release, due to SPM usage of 1.9.0 #1102 issue.)
$ swift package plugin --list output ‘sourcery-command’ (plugin ‘SourceryCommandPlugin’ in package ‘Sourcery’)
Running swift package --allow-writing-to-package-directory sourcery-command failed with error error: the library 'ArticleCardFeature' requires macos 10.13, but depends on the product 'ComposableArchitecture' which requires macos 10.15; consider changing the library 'ArticleCardFeature' to require macos 10.15 or later, or the product 'ComposableArchitecture' to require macos 10.13 or earlier. and the same error for every feature module.
Do I miss something in configuration?
The text was updated successfully, but these errors were encountered:
I am new to Sources and setting up using SPM command plugin.
In the Package.swift file
.package(url: "https://github.com/krzysztofzablocki/Sourcery.git", revision: "3a9e5f1014ac09b30727c01d2a0e1531dac30948")
(use commit of 1.9.2 release, due to SPM usage of 1.9.0 #1102 issue.)$ swift package plugin --list
output‘sourcery-command’ (plugin ‘SourceryCommandPlugin’ in package ‘Sourcery’)
Running
swift package --allow-writing-to-package-directory sourcery-command
failed with errorerror: the library 'ArticleCardFeature' requires macos 10.13, but depends on the product 'ComposableArchitecture' which requires macos 10.15; consider changing the library 'ArticleCardFeature' to require macos 10.15 or later, or the product 'ComposableArchitecture' to require macos 10.13 or earlier.
and the same error for every feature module.Do I miss something in configuration?
The text was updated successfully, but these errors were encountered: