New Release Tag

[code28]

I need the commit 8f94369 in my code, but unfortunately in different libraries, so that SPM doesn't work using another reference than tags. So it'd be great, if you could add a new release tag for master's head. Thank you! 🙏

[johnalanwoods]

SPM let's you use master or a commit:

[code28]

@johnalanwoods I know, but it fails, if your dependency uses this repo as well. (Even if both point to the same commit or branch.)

[infa-jowoods]

Oh wow. Ok. Which other lib are you using out of interest ?

[code28]

It's a private lib I use in different projects. (But I was able to remove the dependency on swift-sodium, so now it's possible to just use a revision in the main project. Nevertheless I think, a new release tag is necessary for swift-sodium.)

[samdowd]

+1 on this

We need the change from https://github.com/jedisct1/swift-sodium/commit/ea3116e481179098b1ed6f0e1c477d5b36a9148d to support iOS 9+ in a pod we're distributing that depends on sodium. Podspecs don't allow us to point to anything other than a specific version number, so we need a version bump (preferably pushed to the pod trunk if possible) to get at that commit. And 0.8.0 won't pass a pod lint because of the Xcode 12 arm64 changes.

Or if anyone has better ideas, happy to hear them. But it does seem like this is a good solution since there's been a libsodium update and some good improvements since the last version bump.

Thanks!

[alexmorrisnz]

Hi @jedisct1 Can you please create a new release tag (and if possible release on CocoaPods CDN) to resolve this?

[Semty]

@jedisct1 any updates?

[jedisct1]

@Semty Any help on getting HKDF and AEGIS bindings that were introduced in libsodium 1.0.19?