Skip to content

build(backend): pin mockery in one place and resolve it via go run - #56

Closed
DoDiODev wants to merge 1 commit into
release-wave9-basefrom
pr/wave9-mockery-pin
Closed

DoDiODev wants to merge 1 commit into
release-wave9-basefrom
pr/wave9-mockery-pin

Conversation

@DoDiODev

Copy link
Copy Markdown
Owner

Fork-only CI evidence for wave 9 (unmodified upstream workflows). Not for merge — will be closed.

@DoDiODev
DoDiODev force-pushed the pr/wave9-mockery-pin branch from d14addb to 66eae7f Compare September 28, 2026 11:48
`backend/Dockerfile` still installed mockery v3.7.2 while the Makefile,
`Dockerfile.local` and `scripts/install-mockery.sh` (used by CI) are on
v3.7.4, so the generated mocks depended on which build path was used.

- Bump the `backend/Dockerfile` pin to v3.7.4.
- Introduce `MOCKERY_VERSION` (default v3.7.4) and
  `MOCKERY ?= GOOS= GOARCH= CGO_ENABLED=0 go run
  github.com/vektra/mockery/v3@$(MOCKERY_VERSION)` in the Makefile;
  `make mock` and `make go-dep` use them. `make mock` thus no longer
  depends on whatever `mockery` is on the PATH (the CI builder image
  `mericodev/lake-builder:latest` ships mockery v2, which cannot read the
  v3 YAML configuration). GOOS/GOARCH are cleared so the tool is built for
  the host even when `backend/Dockerfile` cross-compiles `make all`.
  `MOCKERY=mockery make mock` keeps the old behaviour.
@DoDiODev
DoDiODev force-pushed the pr/wave9-mockery-pin branch from 66eae7f to 053818f Compare September 28, 2026 11:48
@DoDiODev

Copy link
Copy Markdown
Owner Author

Evidence collected via #57 (path filters skip unit-test/e2e for this diff).

@DoDiODev DoDiODev closed this Sep 28, 2026
@DoDiODev
DoDiODev deleted the pr/wave9-mockery-pin branch October 4, 2026 18:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant