-
Notifications
You must be signed in to change notification settings - Fork 458
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
Cut a new release #257
Comments
Unfortunately the project doesn't have resources to do releases. We ship docker images for every main commit. I believe the v2 deprecation README is out of date so we should fix that. |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions. |
The README has not been updated. |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions. |
Still not fixed |
Sorry we don't have the resources to do releases, we publish images on every main commit. |
Apologies for the confusion, the issue was left open because you agreed that the README could do with updating. |
Hi, great project!
I'm a little concerned that there seems to have been a lot of activity since the last release, and there hasn't been a new release yet. I'm also confused about the plans for the deprecation of the v2 API as described in the README - we haven't seen a v2.0.0 yet, though the README talks about it in past tense, when is that planned?
The text was updated successfully, but these errors were encountered: