-
Notifications
You must be signed in to change notification settings - Fork 73
What does the release process look like? #2299
Comments
Apologies for the lack of release. Our team moved out of the project temporarily and making fewer changes. |
TL;DR - you can become maintainer, get permission to release and work with Option 1 indefinitely or fork it and replicate entire infrastructure. Options 1 or 2 :) |
Thank you for chooising this option. Despite us not working on project, you would still have more or less team that will be responsive/help and answer questions etc. |
Release process involves creating tag with the new version in the releases. CI/CD does the rest (unless templates were changed) then we need to push main https://github.com/aerogear/graphback/tree/templates-1.0.0 this branch to release templates. Hope that answers question. Closing for now |
What does the release process look like for this project? I see that the last release as of today is v1.1.2 released on Feb 24, 2021.
If I were to commit support for case sensitivity (see #1967) for Knex, it would seem like it would be very slow moving to actually release into production.
It seems that there's a few options.
ilike
to the knex query mapper.Option 1 is ideal, but it seems that it may never make its way into production.
Option 2 seems best due to Option 1's downside.
Option 3 is soooo far from desirable
The text was updated successfully, but these errors were encountered: