GitHub Action to run Renovate self-hosted for the Apache Solr project.
This action configuration is forked from https://github.com/renovatebot/github-action. See README file in that project for more details.
See .github/workflows/renovate.yml for the workflow and solr/ folder for custom config.
The bot will commit as user SolrBot <solrbot@cominvent.com>.
NOTE: This is a volunteer community project organized by @janhoy, and not
officially run by the Apache Solr PMC. However, Solr committers can enable/disable and re-configure how and when
the project is scanned by this bot. See dev-docs/dependency-upgrades.adoc in the Solr project for details.
If you want to help maintain this bot, start by filing an issue or PR. Solr committers can ask to be given direct commit access.
Maintenance is mainly limited to once in a while updating the version of renovate, and to maintain solr/renovate-config.js.
Also the two secrets RENOVATE_TOKEN and RENOVATE_FORK_TOKEN needs to be re-generated each year. The first should have commit access to solrbot repositories as well as workflow permission. The latter should be a generic github token that is allowed to fork the apache/solr repo.
Some dependency upgrades will require further work in Solr before they pass tests. The PR branches live in a fork of the apache/solr git repository, but Solr committers should be able to commit to the PR branch.