We should ignore the go.mod files in renovate that are inside the
dagger directory, these go.mod files should be updated using
the proper `dagger update` command
Closes#305
Signed-off-by: Jonathan Gonzalez V. <jonathan.gonzalez@enterprisedb.com>
Signed-off-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com>
Signed-off-by: Francesco Canovai <francesco.canovai@enterprisedb.com>
Co-authored-by: Francesco Canovai <francesco.canovai@enterprisedb.com>
Switch to building documentation in markdown, avoiding the
markdown+html hybrid we have.
Closes#250
Signed-off-by: Francesco Canovai <francesco.canovai@enterprisedb.com>
Rework the Dockerfile to list Python dependencies.
Those can be updated using renovate.
Signed-off-by: Francesco Canovai <francesco.canovai@enterprisedb.com>
Signed-off-by: Niccolò Fei <niccolo.fei@enterprisedb.com>
Co-authored-by: Niccolò Fei <niccolo.fei@enterprisedb.com>
Avoid automatic update of dagger module go.mod. It should be updated on
dagger updates.
Signed-off-by: Francesco Canovai <francesco.canovai@enterprisedb.com>
Group all the dagger modules coming from the sagikazarmark/daggerverse
repo in a single renovate PR. This prevents single commits in that repo
to cause multiple PRs in this one.
Closes#118
Signed-off-by: Francesco Canovai <francesco.canovai@enterprisedb.com>
Limit the amount of PRs opened by renovate and also do not auto
rebase the PRs to avoid consuming all the GitHub Runners
Signed-off-by: Jonathan Gonzalez V. <jonathan.gonzalez@enterprisedb.com>
