New release tag

[uny]

New release tag

[Jeehut]

Since I didn't get an answer for nearly two weeks now and this issue is already open for several months, I released a new version myself. Until a new version of FileKit is officially released replace your entry pod "FileKit", "~> 2.0" with pod "Dschee-FileKit", "~> 2.1.1" – that should get you the most current state of the develop branch as of now using my fork here.

[nvzqz]

The next version will be 3.0.0 due to API-breaking changes. Plans for 3.0.0 include cleaning up some ambiguities, making the project SPM-compatible, and new features in general. Apologies for not getting around to an update sooner!

[Jeehut]

Couldn't you simply make a release from commit 020e322 tagged as version 2.1 or 2.0.1? It could take a while until 3.0 is finished – it's already been a while since my fixes and I'm still waiting for a new release. This holds back my CSVImporter framework to be released via CocoaPods (since I can't set my fork as a dependency in the .podspec I have to wait for a release here).

Would be great to get an updated release soon without the breaking changes. Otherwise I'll have to create a separate trunk on CocoaPods which I'd rather like to prevent. I hope this explains my thumbs down.

If the commit I mentioned already includes any breaking changes than you should have been doing them in a separate branch anyway. Otherwise there is no way to fix smaller issues quickly if needed which is something that is very common and should be taken care of.

+1