Skip to content
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

Use dependency bot #40

Closed
zekth opened this issue Dec 12, 2023 · 8 comments · Fixed by #59
Closed

Use dependency bot #40

zekth opened this issue Dec 12, 2023 · 8 comments · Fixed by #59

Comments

@zekth
Copy link
Member

zekth commented Dec 12, 2023

Currently we are maintaining a set of libraries which have dependencies.
Maintaining everything up to date and out of security vulnerability would be quite a mess to do it manually.

I suggest we use Renovate which supports all the language we support.

wdyt?

@jorgelob
Copy link
Contributor

jorgelob commented Dec 12, 2023 via email

@zekth
Copy link
Member Author

zekth commented Dec 12, 2023

dependabot doesn't offer simple strategies regarding to multi languages / grouping etc.
Renovate is free, simpler and more performant from my experience. Easy to setup and offer a simple dashboard also.
One example of what we built at Kong : https://github.com/Kong/public-shared-renovate

@jorgelob
Copy link
Contributor

jorgelob commented Dec 12, 2023 via email

@tasn
Copy link
Contributor

tasn commented Dec 13, 2023

I'm up for either. No strong opinion either way.

@tasn
Copy link
Contributor

tasn commented Dec 28, 2023

@zekth, I don't remember, did we manage to set it up? I remember we had issues.

@zekth
Copy link
Member Author

zekth commented Dec 28, 2023

I ll have a retry run but it was acting weirdly. I think we can setup dependabot in backup solution but renovate is more convenient.

@zekth zekth mentioned this issue Dec 28, 2023
@tasn tasn closed this as completed in #59 Dec 28, 2023
@tasn
Copy link
Contributor

tasn commented Jan 1, 2024

@zekth, I think it's maybe still too aggressive? Should we maybe only tell it to upgrade on security issues?

@zekth
Copy link
Member Author

zekth commented Jan 1, 2024

We were really out of date on many deps, i created one PR to adress the grouping of javascript which is mostly the most noisy ecosystem: #96

Currently the configuration ignores the PATCH and runs weekly. I expect it to be less noisy now that everything has been updated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants