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

Tidy up the dependencies #637

Merged
merged 1 commit into from Jun 1, 2021
Merged

Tidy up the dependencies #637

merged 1 commit into from Jun 1, 2021

Conversation

ccojocar
Copy link
Member

@ccojocar ccojocar commented Jun 1, 2021

No description provided.

@mmorel-35
Copy link
Contributor

mmorel-35 commented Jun 1, 2021

That's weird that you have to do that after each dependencies updates. Isn't there a way to make it done by renovate automatically? Take a look at this https://docs.renovatebot.com/golang/

@ccojocar ccojocar merged commit 8a8dbec into securego:master Jun 1, 2021
@ccojocar
Copy link
Member Author

ccojocar commented Jun 1, 2021

That's weird that you have to do that after each dependencies updates. Isn't there a way to make it done by renovate automatically? Take a look at this https://docs.renovatebot.com/golang/

I agree, it would be cool to fix this stuff. It used to be fine a little while ago.

@mmorel-35
Copy link
Contributor

mmorel-35 commented Jun 1, 2021

A solution might be to remove renovate json config file to trigger a new PR to restart configuration ?
This way we would see what we are doing. The created issue could then be pined and kept active as Babel did. What do you think ?

With this solution we could reschedule to weekly update for example and make renovate handle github-actions versioning.
Then dependabot would be removed so there would only be one bot to handle everything

@ccojocar ccojocar deleted the update-deps branch May 13, 2024 16:17
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 this pull request may close these issues.

None yet

2 participants