Skip to content

build: prepare legacy Go 1.27.3 security release - #256

Merged
Roasbeef merged 3 commits into
v0.2from
release/v0.2-go1273
Oct 21, 2026
Merged

Roasbeef merged 3 commits into
v0.2from
release/v0.2-go1273

Conversation

@Roasbeef

Copy link
Copy Markdown
Member

In this PR, we prepare the legacy v0.2 line for a Go 1.27.3 security
release, starting from the released v0.2.19-alpha source. We keep the
Bitcoin package identities and runtime dependency versions unchanged.
The btcsuite-v2 migration in #255 stays on master and isn't part of this
release branch. The already released sqldb/v2 changes remain intact.

We align module, Docker and CI toolchains and move the linter to
v2.15.0. The configuration preserves the prior check set, including the
former gosimple checks now grouped under staticcheck. We also check the
actual errors returned by three integration-test helper paths. No tests
are removed or skipped. Regenerated RPC differences are comments only;
message descriptors, fields and methods are unchanged.

Validation

On Go 1.27.3, unit and race tests, the application build, scoped vet,
frdrpc tests/build/vet, all three module tidy checks and integration-test
binary compilation pass. The fresh Docker tools build runs linter
v2.15.0 with zero issues. Clean-tree formatting, module and RPC generation
checks pass. Integration-node and Postgres runtime tests weren't run
locally; remote CI remains required.

The base branch is v0.2, created from v0.2.19-alpha so this diff doesn't
revert the migration on master. A PR to this slash-free base also matches
the existing CI branch filter. No workflow deployment triggers are
broadened, and no tag or release has been created.

  • Pass remote CI before merging.
  • Confirm the next patch version and release metadata before tagging.

@Roasbeef
Roasbeef merged commit b547bae into v0.2 Oct 21, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant