Repository navigation
ci: run CI jobs in apache/devlake:lake-builder-v0.0.17 - #9409
Merged
Merged
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: DoDiODev <DoDiDev@proton.me>
klesh
approved these changes
Nov 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Follow-up to #9378. Now that
builder-v0.0.17has been published asapache/devlake:lake-builder-v0.0.17(thanks!), the five CI jobs move fromlake-builder-v0.0.16to the new tag:test.yml(unit-test)test-e2e.yml(e2e-mysql, e2e-postgres)golangci-lint.ymlmigration-script-lint.ymlThe new image reflects the builder changes merged since
v0.0.16: Debian 13(trixie) with Python 3.14 (#9378), no libgit2 (#9293), mockery 3.9.0 (#9302)
and uv 0.13.8 (#9364, #9392). Go stays at 1.27.3.
The job steps are unchanged; Go and mockery are still installed from
backend/scripts/.Does this close any open issues?
No.
Other Information
I ran the steps of
test.yml(tidy and pluginsgen checks, build-python,unit tests) and
migration-script-lint.ymllocally inside the publishedlake-builder-v0.0.17image; all passed. My fork's CI builds the sameDockerfile and runs all five jobs in it. The CI run of this PR is the
first run on the published image.
actionlintreports no new findings forthe changed workflows.