Open mmorel-35 opened 11 months ago
Change dependabot updates schedule interval to "weekly" to address updates more frequently so it doesn't become an epic task every month ?
We already had that schedule, and there were lots of updates, exhausting the free tier of our GH actions workers across the entire testcontainers organisation.
I guess that at that time there was no groups for the updates. Would it helps smooth the process? Another option would be to replace dependabot with renovate.
Move Image of the example/module to a Dockerfile to be able to receive updates from dependabot ?
Regarding this, I'd say no, as we want to keep modules stable, at least until we have a real support matrix (which we do not have). Also moving to a Dockerfile-based module will force users to build the image again and again.
Just in case, I'm exploring updatecli for certain updates
Proposal
There are several ideas I can see concerning testcontainers-go, some concerning modulegen, some concerning the CI/CD.
Modulegen
extract mkdocs#1543example.md
file generation in/internal/mkdocs
extract#1537Makefile
file generation in/internal/make
extract#1539example.go
andexample_test.go
file generation in/internal/module
extract#1539go.mod
file generation in/internal/module
and replace html/template withgolang.org/x/mod/modfile
to directly read from maingo.mod
use#1550github.com/spf13/cobra
to handle the commandsCI/CD
Provide code coverage to sonarcloud (starting with main module)#1518Generate sonar-project.properties per module/example ?Change dependabot updates schedule interval to "weekly" to address updates more frequently so it doesn't become an epic task every month ?Move Image of the example/module to a Dockerfile to be able to receive updates from dependabot ?I'm much more focused on modulegen for the moment