Repository navigation
build: bump mockery to 3.9.0 and golangci-lint to 2.15.0 - #9302
Merged
Merged
Conversation
mockery 3.9.0 regenerates byte-identical mocks; the SHA256 values in install-mockery.sh are taken from the release checksum.txt and verified against the downloaded archives. The lake-builder image needs a new builder-v* tag before CI picks up the new mockery. Signed-off-by: DoDiODev <DoDiDev@proton.me>
klesh
approved these changes
Nov 2, 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
Bumps two Go build tools:
backend/Makefile(MOCKERY_VERSION),backend/scripts/install-mockery.sh(version and sha256 checksums forx86_64 and arm64),
backend/Dockerfile,backend/Dockerfile.local,devops/docker/lake-builder/Dockerfile, and the step names ingolangci-lint.ymlandtest.yml.golangci-lint.ymlandbackend/Makefile.The
lake-builderimage needs a new tag for the Dockerfile change. Once thisis merged, could a committer push
builder-v0.0.17? I will then send afollow-up PR that moves the five
container:pins fromlake-builder-v0.0.16tov0.0.17. That image will also no longer containlibgit2, since #9293 removed it from the Dockerfile.
Does this close any open issues?
N/A
Screenshots
N/A
Other Information
make mockwith 3.9.0 produces mocks that are byte-identical to 3.8.1(no changes under
backend/mocks/).and Postgres, config-ui, license header, Grafana check; 14/14 jobs green):
https://github.com/DoDiODev/devlake/actions/runs/41415891071