Repository navigation
Chore: upgrade and pin Go development tools - #277
Merged
Merged
Conversation
Conventional Commits Report😢 No conventional commits found. 👉 Learn more about the conventional commits usage at Greenbone. |
mgoetzegb
marked this pull request as ready for review
November 3, 2026 13:10
alex-heine
approved these changes
Nov 6, 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.
What
Update and pin the Makefile's Go tools against latest stable upstream tags checked on 2026-11-02:
Regenerate mocks with Mockery v3.9.0; the generated changes mark constructors and cleanup callbacks as test helpers. SWAG v2 release candidates were excluded. Old/new SWAG generation produced identical API files; existing generated-document drift was excluded.
Compatibility: go.mod declares Go 1.26.8; SWAG requires Go 1.18 and the other selected tool modules require Go 1.26.0. CI selects stable Go and Docker pins 1.27.3. Runtime validation used Go 1.27.3 with GOFLAGS=-buildvcs=false.
Passed:
make generate-code,make api-docs,make build,go test ./... -run '^$',make lint(0 issues),make govulncheck(0 reachable symbol vulnerabilities; 3 vulnerabilities in required modules with no affected calls found),go test ./... -count=1 -timeout=180swith a dedicated disposable PostgreSQL 16 instance, andgit diff --check. The initial web-test attempt without PostgreSQL failed on connection refusal; the complete rerun passed after starting the isolated database. Go 1.26.8 runtime and container/product E2E were not tested.Why
Use current stable tooling and make lint and vulnerability scans reproducible instead of resolving moving @latest versions on each run.
Checklist