Skip to content
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

Fix version for Komondor #162

Merged
merged 2 commits into from
Aug 2, 2022

Conversation

redryerye
Copy link
Contributor

@redryerye redryerye commented Aug 2, 2022

Komondor had a release for v.1.1.4 where it added unnecessary dependencies that will only be used in Komondor's development process.
It would be great if we could minimize dependencies to avoid SPM conflicts by not updating Komondor to v1.1.4.

Right now, Sourcery as a SPM plugin is facing a conflict because of this.

@krzysztofzablocki
Copy link
Contributor

@djbe this is a big issue for Sourcery

@djbe
Copy link
Member

djbe commented Aug 2, 2022

Ugh this is annoying TBH, Komondor should release a new version with those dependencies hidden again 🤦

But then again, should we be hiding dependencies like Komondor ourselves as well? What about testing dependencies like Spectre (from Stencil)? Although Komondor is definitely the biggest issue, because it includes quite a lot of big packages.

@djbe djbe merged commit 4eb36c8 into SwiftGen:stable Aug 2, 2022
@djbe djbe added this to the 2.10.1 milestone Aug 2, 2022
@redryerye redryerye deleted the feature/fix-komondor-version branch August 3, 2022 01:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants