DoDiODev opened a new pull request, #9271: URL: https://github.com/apache/devlake/pull/9271
### Summary Follow-up to #9267. Now that `builder-v0.0.16` has been published as `apache/devlake:lake-builder-v0.0.16`, the five CI jobs that still ran in `mericodev/lake-builder:latest` use it instead: - `test.yml` (unit-test) - `test-e2e.yml` (e2e-mysql, e2e-postgres) - `golangci-lint.yml` - `migration-script-lint.yml` `mericodev/lake-builder:latest` was last updated in 2023 (bullseye, Go 1.20). The new image is built from the current `devops/docker/lake-builder/Dockerfile` (bookworm, Go 1.27.3, libgit2 1.5.0, Python 3.11) and is pinned to an explicit tag, so future builder updates are a deliberate one-line change. The job steps themselves are unchanged. They still install libgit2, Go and mockery from `backend/scripts/`, so the pinned toolchain versions remain the ones defined in the repository. ### Does this close any open issues? Closes #9209 ### Other Information My fork's CI builds the same Dockerfile and runs these job steps in it (unit, lint, migration lint, e2e on MySQL and PostgreSQL). The CI run of this PR is the first run on the published image. `actionlint` reports no new findings for the changed workflows. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
