fix(security): build harbor-cli with Go 1.26.4#19
Conversation
Bump the go directive to 1.26.4 so the dagger release build uses golang:1.26.4-alpine, fixing Go stdlib vulnerabilities reported by redline static scan on harbor-connector-automatic-creation:v0.0.18: - CVE-2026-42504 (HIGH) - CVE-2026-27145 (MEDIUM) - CVE-2026-42507 (MEDIUM)
Welcome to Codecov 🎉Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests. ℹ️ You can also turn on project coverage checks and project coverage reporting on Pull Request comment Thanks for integrating Codecov - We've got you covered ☂️ |
|
Verification note: ran This is expected: a patch-level bump of the Also verified |
|
/ready |
Summary
Bump the
godirective ingo.modfrom 1.26.3 to 1.26.4. The dagger release build derives thegolang:<version>-alpinebuilder image from this directive, so the nextv0.0.18-alauda-*release will be built with Go 1.26.4.This fixes the Go stdlib vulnerabilities reported by the redline static scan against
connectors-operator-bundle:v1.11.0-rc.192.ge8c3a01(imagedevops/harbor-connector-automatic-creation:v0.0.18, binary/usr/local/bin/harbor-cli):Same pattern as #17 (previous Go 1.26.3 security bump).
Follow-up after merge
v0.0.18-alauda-11and the release workflow will publish binaries built with Go 1.26.4.HARBOR_CLI_VERSIONtov0.0.18-alauda-11inconnectors-extensions(connectors-harbor/tektoncd/tasks/harbor-connector-automatic-creation/0.1/images/harbor-cli/Containerfile) and trigger/test harbor-connector-automatic-creation.Test plan
go build ./...passes locally with Go 1.26.4