Alberto Bertogli d2260180c6 github: Note that govulncheck is run on the latest Go version ...

When running govulncheck, if we use go.mod's version, that is the oldest
Go version that we expect to build chasquid.

However, that specific version is often 1.x.0 and can include
vulnerabilities that are fixed in later patch releases. This can cause
govulncheck to complain, which introduces noise in the CI.

Instead, we should run govulncheck on the latest Go version, to make
sure that any reports are about our code or the dependencies, and not
the toolchain.

That behaviour is in place today, but it's not obvious from the config.

This patch updates the config to note this more explicitly, to prevent
future confusion.

2026-10-04 19:03:09 +01:00

..

workflows

github: Note that govulncheck is run on the latest Go version

2026-10-04 19:03:09 +01:00