We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
There should be a dependabot or renovate to help keep dependencies up to date.
This helps keep dependencies update and does not require manually upkeep to update them.
Give it a 👍 We prioritize the features with most 👍
The text was updated successfully, but these errors were encountered:
This is a good point. TBH, I want to introduce the dependabot, but our CI testing is too flaky in building images and unit/integration/e2e testing.
So, I would like to postpone the dependabot until the v1 API is removed.
Sorry, something went wrong.
I think, we already have it, isn't ? Here is the PR example: #2056
That is created by the critical security issue. Kevin indicates to add a depandabot script so that we can always use the latest library version.
Oh, I see, thanks for the clarification! /remove-label lifecycle/needs-triage /area engprod
No branches or pull requests
What you would like to be added?
There should be a dependabot or renovate to help keep dependencies up to date.
Why is this needed?
This helps keep dependencies update and does not require manually upkeep to update them.
Love this feature?
Give it a 👍 We prioritize the features with most 👍
The text was updated successfully, but these errors were encountered: