chore(deps): upgrade Go from 1.24.0 to 1.26.1

[flexiondotorg]

• Update go.mod to Go 1.26.1
• Update flake.nix to use go_1_26 package

[cubic-dev-ai]

1 issue found across 2 files

Confidence score: 3/5

• There is a concrete compatibility risk in go.mod: raising the go directive can force consumers onto a newer Go toolchain, which is a breaking change for a library if not strictly required.
• Given the issue’s medium severity (6/10) and high confidence (8/10), this is more than a housekeeping tweak and may impact downstream users’ build environments.
• Pay close attention to go.mod - confirm the higher minimum Go version is truly needed by this PR before merging.

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="go.mod">

<violation number="1" location="go.mod:3">
P2: This `go` directive unnecessarily raises the module's minimum supported toolchain. For a library module, that is a breaking compatibility change unless the code actually needs Go 1.26 features or fixes.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[cubic-dev-ai]

1 issue found across 7 files (changes from recent commits).

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name=".github/workflows/ffmpeg-test.yml">

<violation number="1" location=".github/workflows/ffmpeg-test.yml:42">
P2: Because this job now reads the Go version from `go.mod`, `go.mod` changes need to trigger the workflow too. Otherwise Go upgrades can merge without ever running the FFmpeg build on the new toolchain.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[cubic-dev-ai]

1 issue found across 2 files (changes from recent commits).

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="internal/builder/libraries.go">

<violation number="1" location="internal/builder/libraries.go:910">
P2: Propagate the `filepath.WalkDir` error instead of discarding it.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}