fix(flow): upgrade to go 1.27

[itsbilal]

Bumps version of Go up to 1.27.

Only changes were some transitive
dependency bumps (pebble, swiss) and transposing the Error() method on
some errors that also have an Unwrap() method so that the pointer type
itself also implements the error interface, which govet now enforces
more strongly when an error is formatted with %w. Other lint changes
were removing excess parenthesis and always-nil return values.

[claude]

Code review

flow/go.mod:3 — The go directive now requires 1.27.0, but the Go toolchain pins used to build and lint this module are still on 1.26 and were not bumped in this PR.

The flow builder image is pinned to 1.26:

peerdb/stacks/flow.Dockerfile

Lines 2 to 4 in a12f5ce

	FROM golang:1.26-alpine@sha256:0178a641fbb4858c5f1b48e34bdaabe0350a330a1b1149aabd498d0699ff5fb2 AS builder
	# Allow build flags to be passed in at build time, for example debug flags

The official golang images set ENV GOTOOLCHAIN=local, so no newer toolchain is downloaded, and there is no toolchain directive in flow/go.mod (nor any GOTOOLCHAIN override anywhere in the repo). The first Go step in the builder stage (go mod download) therefore fails with go: go.mod requires go >= 1.27.0 (running go 1.26.x; GOTOOLCHAIN=local). This breaks all four images built from stacks/flow.Dockerfile (flow-api, flow-worker, flow-snapshot-worker, flow-maintenance) — and both docker-build (ubuntu-latest) and lint are currently failing on this PR after ~20s.

The same stale pin exists in the workflows (these only survive because actions/setup-go leaves GOTOOLCHAIN=auto and silently downloads 1.27 at build time, which defeats the pin):

• .github/workflows/golang-lint.yml:27 — go-version: 1.26.6
• .github/workflows/tilt-flow.yml:235 — go-version: 1.26.6
• .github/workflows/cleanup.yml:17 — go-version: 1.26.6

Suggested fix: bump stacks/flow.Dockerfile to golang:1.27-alpine (with the matching digest) and update the three go-version pins to a 1.27.x release.

The error-type refactor itself (embedded error -> named err field plus explicit Error()) checks out: field order is preserved for the positional literals, the one keyed literal was renamed, all external usages go through the constructors or errors.AsType[*T], and no new nil-panic surface is introduced.

_{🤖 Generated with Claude Code}

[github-actions]

⚠️ Deprecated destination connector

This issue or pull request relates to a deprecated destination connector (Snowflake, BigQuery, ElasticSearch, Kafka, Redpanda, Confluent, Azure Event Hubs, Google Pub/Sub, or S3).

These destinations are no longer actively maintained, but remain functional. We are unlikely to prioritize new work here.

Note: BigQuery is deprecated only as a destination — it remains a supported source.

If you depend on one of these connectors, we recommend:

• Pin to a known-good PeerDB version so behavior stays stable.
• Fork the repository if you need to carry your own changes.

See the deprecated connectors documentation for details and migration guidance.

[github-actions]

❌ Test Failure

Analysis: Not flaky: the PR bumps flow/go.mod to go 1.27.0 but the workflows still pin actions/setup-go to 1.26.6 with GOTOOLCHAIN=local, so go mod download fails deterministically before any test runs.
Confidence: 0.98

⚠️ This appears to be a real bug - manual intervention needed

View workflow run

[itsbilal]

There's some overlap here with #4753. I'll re-trigger the bot on that branch to pick up the rest if this one merges first.

[ilidemi]

Nice!