Repository navigation
chore(deps): bump github.com/vektah/gqlparser/v2 from 2.5.63 to 2.5.64 #2110
Workflow file for this run
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
| name: Lint | |
| on: | |
| push: | |
| branches: | |
| - main | |
| pull_request: | |
| branches: | |
| - main | |
| jobs: | |
| lint: | |
| runs-on: ubuntu-latest | |
| steps: | |
| - name: Checkout code | |
| uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1 | |
| - name: Install Go | |
| uses: actions/setup-go@b7ad1dad31e06c5925ef5d2fc7ad053ef454303e # v7.0.0 | |
| with: | |
| go-version-file: go.mod | |
| cache-dependency-path: go.sum | |
| # golangci-lint is currently advisory on this repo: the fork is on | |
| # Go 1.26 and earlier golangci-lint releases refuse to lint a newer | |
| # toolchain than they were built with. Once a stable v2.x is pinned | |
| # and known to produce a clean run against this codebase, drop the | |
| # continue-on-error flags on the retries. | |
| - name: Lint | |
| uses: golangci/golangci-lint-action@ba0d7d2ec06a0ea1cb5fa41b2e4a3ab91d21278a # v9.3.0 | |
| continue-on-error: true | |
| id: lint_first_try | |
| with: | |
| version: latest | |
| args: --config .golangci.yml -v | |
| - name: Lint Retry 1 | |
| if: steps.lint_first_try.outcome == 'failure' | |
| uses: golangci/golangci-lint-action@ba0d7d2ec06a0ea1cb5fa41b2e4a3ab91d21278a # v9.3.0 | |
| continue-on-error: true | |
| id: lint_retry_1 | |
| with: | |
| version: latest | |
| args: --config .golangci.yml -v | |
| - name: Lint Retry 2 | |
| if: steps.lint_retry_1.outcome == 'failure' | |
| uses: golangci/golangci-lint-action@ba0d7d2ec06a0ea1cb5fa41b2e4a3ab91d21278a # v9.3.0 | |
| continue-on-error: true | |
| id: lint_retry_2 | |
| with: | |
| version: latest | |
| args: --config .golangci.yml -v | |
| # Supply-chain vuln scan. Unlike golangci-lint above (advisory while the | |
| # Go 1.26 toolchain outpaces stable linter releases), this job GATES: a | |
| # known-vulnerable dependency or stdlib version should block the merge. | |
| # govulncheck is call-graph aware — it only flags advisories whose | |
| # vulnerable symbols are actually reachable from this codebase, so it | |
| # stays quiet on unreachable transitive CVEs. | |
| govulncheck: | |
| runs-on: ubuntu-latest | |
| steps: | |
| - name: Checkout code | |
| uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1 | |
| - name: Install Go | |
| uses: actions/setup-go@b7ad1dad31e06c5925ef5d2fc7ad053ef454303e # v7.0.0 | |
| with: | |
| go-version-file: go.mod | |
| cache-dependency-path: go.sum | |
| # Invoke govulncheck directly rather than via golang/govulncheck-action. | |
| # The wrapper action manages its own checkout + Go install with pinned | |
| # sub-actions (actions/checkout@v4.1.1, actions/setup-go@v5), which here | |
| # caused two problems on top of the version it actually ran under: | |
| # - its bundled checkout auth collided with our actions/checkout@v7 | |
| # (`Duplicate header: "Authorization"` → HTTP 400), and | |
| # - it carries a default `go-version: stable`, so passing go-version-file | |
| # produced a "both specified, only go-version used" warning and would | |
| # have scanned under `stable` instead of the go.mod toolchain. | |
| # Since the checkout + setup-go steps above already put the go.mod Go on | |
| # PATH, running the tool directly is simpler and removes the version | |
| # ambiguity — govulncheck's stdlib advisories are toolchain-version | |
| # specific, so scanning under the version we actually ship matters. | |
| # govulncheck is version-pinned (not @latest) so a new tool release | |
| # can't flip CI red on an unrelated day — reproducible CI needs pinned | |
| # tooling. Dependabot's gomod updates don't cover this `go install`, so | |
| # bump the tag here deliberately. The job is a hard gate: govulncheck | |
| # exits non-zero when a vulnerable symbol is actually reachable, which | |
| # fails the step. Findings are stdlib/dep CVEs that are reachable from | |
| # our code; the usual fix is a Go toolchain bump (the patched stdlib | |
| # versions ride a Go point release), not a code change. | |
| - name: Run govulncheck | |
| run: | | |
| go install golang.org/x/vuln/cmd/govulncheck@v1.5.0 | |
| govulncheck ./... |