-
Notifications
You must be signed in to change notification settings - Fork 23
document support for query params #66
Comments
We've actually stopped using semver.io in all official buildpacks, and it's not really being actively maintained beyond security updates. I'm happy to merge a PR, but would you be interested in taking back ownership? |
I kinda thought that might be the case. Are you using another service now instead? Solving the range resolution problem a different way? |
Unfortunately, no. I don't have enough of a need for it right now to take that on. |
We're using a new service: https://nodebin.herokai.com/ that replaces s3pository and semver.io but is not open source |
Cool. Is the outside world (e.g. the @probot org) welcome to use this service? |
Ideally not. Currently it only serves Node binaries, but this is likely to be extended in the near future to do things like:
While any iterations will be versioned, we're not really intending for the service to be consumed by third-parties. What is the use-case for @probot? Is it met by semver.io? |
Okay thanks for the clarification. semver.io was a longshot solution for probot/friction#29 |
Even with no buildpacks using it, semver.io is still receiving ~80k requests / day during the week which is why we haven't taken it down. Ideally we could pass it off to community owners somehow. |
That warms my heart :) |
Maybe we could start a fund for it with OpenCollective or something. Any idea who's using it? Forked buildpacks mostly? |
Hi @jmorrell !!!
I want to open a PR documenting support for the
range
query param:Before I do so, just want to make sure it's wanted, and that it has a chance of being merged :)
The text was updated successfully, but these errors were encountered: