Closed ferologics closed 3 years ago
@stephencelis you're right, this isn't necessary.
We recently started using both TCA
& CCL
. In some modules we cannot link TCA
, only CCL
b/c it already exports TCA
with it. We're not version locking our dependencies, and I was seeing some funky behavior, so my initial thought was that maybe SPM is mistakingly importing a wrong version of TCA
(declared in CCL
). Fortunately, this is not the case, as SPM correctly resolves the main TCA
package version.
Hey @ferologics! Thanks for the PR. We think, though, that you should be able to use 0.18.0 already, though, since by default the
from: "0.9.0"
should favor the latest minor version, which is"0.18.0"
.If you wanna upgrade a project in Xcode, you can Update to Latest Package Versions from the SPM menu, or you can run
swift package update
for non-Xcode projects. Were you encountering a situation where you were unable to upgrade to the latest version of TCA?