Tim Condon

One thing this PR doesn't currently change is the CMake files - will wait to hear if it should be a breaking or backwards compatible change first

Linking to the forum threads discussion to make CryptoExtras the main library and `CryptoCore` what is currently `Crypto`. Also discussions around package traits https://forums.swift.org/t/improving-crypto-on-all-platforms/75330/37

@Lukasa following on from https://github.com/apple/swift-crypto/pull/359 - do we want to stick with this PR or go for another name to `CryptoExtras`

I would be happy with that!

`ExtendedCrypto` is the best option I've seen if the decision is to keep `Crypto` as is. I'm still in favour of `CryptoEssentials` for my vote but would be happy with...

Closing in favour of #407

Yeah I don't think calling it multiple times was intended to be supported, it just works in some cases. I'm hesitant to go messing around with the state machine given...

You might have to try it, I don't think anyone has yet

I don't think this is supported behaviour. The `@Group` is supposed to be all fetched so that we can populate it correctly. I'd say if you need to retrieve specific...

@mikhailkoliada is there a way to use the new image or speeding up the deployment? We're using Docker so I don't think the workaround will work and all our builds...