Repository navigation
build: prepare legacy Go 1.27.3 security release - #256
Merged
Merged
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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'trevert 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.