There appears to be an inconsistency between the v0.7 branch and the 0.7.0 tag.
The tag appears to point to a commit that looks like work in progress for 0.8.0. It's not on any branch that the swiftcsv/SwiftCSV remote knows about.
I'd recommend that we move directly to 0.7.1 as the first "0.7.x" release to Cocoapods and don't even try to release 0.7.0. Please let me know if you don't agree.
It's possible that someone using Swift Package Manager may have picked up 0.7.0, because SwiftPM looks at tags, not branches or GitHub releases. The semantic versioning 2.0 spec is silent on deleting an unintended release; it just says you can't change it. So I don't think we'd be breaking any rules if we simply deleted the 0.7.0 tag. Again, please let me know if you don't agree.
There appears to be an inconsistency between the v0.7 branch and the 0.7.0 tag.
The tag appears to point to a commit that looks like work in progress for 0.8.0. It's not on any branch that the swiftcsv/SwiftCSV remote knows about.
I'd recommend that we move directly to 0.7.1 as the first "0.7.x" release to Cocoapods and don't even try to release 0.7.0. Please let me know if you don't agree.
It's possible that someone using Swift Package Manager may have picked up 0.7.0, because SwiftPM looks at tags, not branches or GitHub releases. The semantic versioning 2.0 spec is silent on deleting an unintended release; it just says you can't change it. So I don't think we'd be breaking any rules if we simply deleted the 0.7.0 tag. Again, please let me know if you don't agree.