Repository navigation
ci: check chain versions before tagging - #1500
Open
yyforyongyu wants to merge 3 commits into
Open
yyforyongyu wants to merge 3 commits into
yyforyongyu wants to merge 3 commits into
Conversation
yyforyongyu
commented
Nov 12, 2026
yyforyongyu
force-pushed
the
task-chain-versions
branch
2 times, most recently
from
November 12, 2026 11:28
ffed234 to
006da95
Compare
yyforyongyu
commented
Nov 12, 2026
yyforyongyu
force-pushed
the
task-chain-versions
branch
2 times, most recently
from
November 12, 2026 13:49
2837619 to
d67bc9e
Compare
yyforyongyu
force-pushed
the
task-chain-versions
branch
from
November 13, 2026 10:35
d67bc9e to
311423a
Compare
yyforyongyu
marked this pull request as ready for review
November 14, 2026 21:20
Keep ordinary integration checks on current authenticated daemon releases. Share Core archive and btcd exact-tag installers across workflow calls, and reject checksum or installed-version mismatches before tests start. Keep compiler selection local to btcd installation so wallet tests use the configured Go version.
Select the latest stable patch from the three newest Core major lines using upstream release metadata and official archive checksums. Read the current btcd pin from ordinary CI and combine it with the selected previous release. Publish one complete matrix and its current miner tag only after all discovery succeeds.
Run full normal CI plus five complete SQLite compatibility lanes on every release branch push before maintainers publish signed tags. Reuse the normal workflow at the candidate commit and isolate its concurrency group from the release caller. Resolve the latest three stable Core major lines and retain the selected previous btcd release. Share the canonical current pin from normal CI with the release rows and Core miner. Document tagging the exact passing candidate SHA.
yyforyongyu
force-pushed
the
task-chain-versions
branch
from
November 14, 2026 22:00
311423a to
52fec23
Compare
Coverage Report for CI Build 43645782616Warning No base build found for commit Coverage: 62.224%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsRequires a base build to compare against. How to fix this → Coverage Stats
💛 - Coveralls |
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.
Summary
Implement task 451: every push to a release branch runs full normal CI plus five SQLite chain-version checks before tagging. Bitcoin Core versions are discovered automatically from upstream stable releases.
Change Description
v0.19-branchfrom maintainedsql-walletafter this workflow is present. Pushes tov0.*-branch, including subsequent fixes without a version bump, automatically startRelease checks. Ordinary PRs retain normal CI.normal-cicalls the existing CI workflow from the same candidate commit: static/generated checks, lint, unit/race tests, database integration and current-version chain tests. PR commit-range validation retains its existing PR-only guard. Separate concurrency groups prevent the nested CI from cancelling its release caller.fetch-chain-backend-versionsdiscovers the latest stable patch of the three newest Core major lines and their official archive checksums.itest-chain-backend-versionsruns the complete SQLite suite for those releases plus btcd v0.27.0/v0.26.2. Core uses the latest selected btcd miner; Neutrino stays current-only in normal CI.main.yml; discovery shares it with the current release row and Core miner. Shared installers verify authenticated artifacts/modules and exact running daemon versions. After the full release run passes, a maintainer signs and pushes the tag at that exact tested SHA. These jobs do not create tags or publish release artifacts. Manual selected-ref retries become available once the workflow is also on defaultmaster; automatic release-branch pushes only require it on that branch.Notes
The Core window currently resolves to 32.1, 31.2 and 30.4. The canonical-pin regression reproduces the prior drift and verifies that one main-workflow edit updates ordinary CI, the release row and the Core miner. Workflow/branch/call/concurrency validation, actionlint/ShellCheck, discovery fixtures and live discovery pass. All three signed commits compile independently and stay below 150 weighted additions. The complete representative Core 32.1/SQLite suite passes on maintained tip 1d3cc4d.
Earlier verification covered all ten distinct ordinary/release configurations, including successful full suites for all five selected daemons on a prior base. On base 7a8079e, four lanes passed while btcd v0.26.2 timed out waiting for the miner reorg in both full attempts. Those failures and earlier passing repeats remain recorded; this pin correction changes no daemon, harness or scenario and adds no skip or CI retry. A failing compatibility lane continues to block release success.