Dependabot bumps are currently handled by everyone. In the same way this sometimes feels like nobody is responsible. Therefore we want to have one or two dedicated people per repo who do take care of the bumps. This doesn't mean anyone else must not review/merge bumps. It rather means if bumps are not taken care of, especially in the case of security fixes and critical bug fixes, we know who's the right person to have a look.
Many repos have different ecosystems to maintain. E.g. Mail has github action, composer and npm bumps. We can and should distribute this to more than one person to avoid a bottle neck.
Describe the task
Dependabot bumps are currently handled by everyone. In the same way this sometimes feels like nobody is responsible. Therefore we want to have one or two dedicated people per repo who do take care of the bumps. This doesn't mean anyone else must not review/merge bumps. It rather means if bumps are not taken care of, especially in the case of security fixes and critical bug fixes, we know who's the right person to have a look.
Many repos have different ecosystems to maintain. E.g. Mail has github action, composer and npm bumps. We can and should distribute this to more than one person to avoid a bottle neck.
Affected components
To do
dependabot.yml
renovate.json