I see it notes OpenAPI 3.1 support, but it's using kin-openapi which doesn't yet support OpenAPI - how have you managed that?
(speaking as someone building on top of kin-openapi, as a core maintainer for oapi-codegen)
https://blacksmoke16.github.io/oq/ | https://github.com/Blacksmoke16/oq
(as I discovered when I installed oq via homebrew to find myself with a different app)
That leads to the second thing which is that you said you "added binaries" but your release artifacts are .tar.gz which means that one now needs to `curl -fSL | tar -xzf - -C /whatever` and deal with whatever interior directory scheme you are using (I didn't check)
I suspect I may be throwing good commentary after bad, but if you did want to participate in Brew distribution, but don't want to go through their stupid PR process, you can retain control over your update schedule by creating a "Brew Tap" and then the consumer would (e.g.) `brew tap plutov/brew && brew install plutov/brew/oq` which also gets away from the naming collision
You do have a naming conflict though unfortunately so I’m not sure how you would deal with that.
rtk0•4mo ago