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

Is there any reason multipart-kit requires macOS 10.15? #77

Closed
adam-fowler opened this issue Oct 1, 2021 · 2 comments · Fixed by #78
Closed

Is there any reason multipart-kit requires macOS 10.15? #77

adam-fowler opened this issue Oct 1, 2021 · 2 comments · Fixed by #78
Labels
bug Something isn't working

Comments

@adam-fowler
Copy link
Contributor

No description provided.

@adam-fowler adam-fowler added the bug Something isn't working label Oct 1, 2021
@0xTim
Copy link
Member

0xTim commented Oct 2, 2021

Likely a hang up as it was extracted from Vapor. There's nothing that requires 10.15 in here at the moment though Vapor packages took the approach of adding it to everything to avoid breaking changes at later dates.

I'm pretty sure we could add it in if needed in a non-breaking change as SwiftPM should resolve it correctly and just pick the oldest version right? I can't imagine us needed to use Crypto, which is the only thing that mandates 10.15 in the chain, so I'm happy to open this up.

Thoughts @siemensikkema?

@siemensikkema
Copy link
Member

+1 on removing the restriction 👌🏻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants