poc: update extensions with renovate #3241
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a POC for how renovate could be used to automate the update of the extensions.
It works by using a custom datasource that fetches the extension.toml from each extension repo to check if it matches extensions.toml in this repo and then bumps extensions.toml.
Additional one could run a script that then updates the git submodule of the updated extension (using renovates postUpgradeTasks (this requires self-hosting renovate i guess) or an CI job).
The poc only works for github repos currently is very hacky but I would like to know if you would be interested in this. I think the automation potential is huge since updating the submodules manually is quite error prone.
See qvalentin#9 for an example PR of renovate.