Patrick T Coakley

Just bumping this to see what the status is, or do we want to close it and revisit it with a proper Issue?

Just bumping to see if this is still possible? I think both this and an exposed Help/Version method would be ideal.

Would it make sense to cache the releases locally on bootstrap and gate them based on arch/platform for at least the minimum available versions and periodically update it?

Yeah that makes sense as a design goal and changes how I might interpret some things, thanks for clarifying.

Hey, I'd be interested in trying to help with this effort when I have free cycles. Currently I am getting: ``` C:\Users\patri\Source\repos\swiftly\.build\checkouts\swift-openapi-generator\Sources\_OpenAPIGeneratorCore\PlatformChecks.swift:21:5: error: _OpenAPIGeneratorCore is only to be used by...

Also worth considering just adding [Atom](https://en.wikipedia.org/wiki/Atom_(web_standard)) support since many SSGs just do that and most RSS readers can read Atom.

It looks like [this issue](https://github.com/apple/swift-openapi-generator/pull/753) might at least unblock OpenAPI generator for some forward progress. I did take a look at NIO and there seems to been some progress going...

> This is the main tracking issue [apple/swift-nio#2065](https://github.com/apple/swift-nio/issues/2065). FWIW NIO should get Windows support in the next few months That's great to hear! Is there somewhere that mentions this? The...

Thanks for the update, @czechboy0! Once I bumped the minimum versions of `swift-openapi-generator` and `swift-openapi-runtime` to 1.7.2 and 1.8.2, respectively, I'm able to hit NIO compilation errors, which is expected....

Ok, feel free to close and I'll make an issue there.