Repository navigation
Rebuild 2.20.1 on Ubuntu 24.04 with updated ca-certificates (eMudhra CA revocation) - #24041
Merged
Merged
Conversation
…CA revocation) Bump the final image base from ubuntu:20.04 to ubuntu:22.04 in both Dockerfiles so the image picks up ca-certificates 20260816ubuntu0.22.04.1 (20.04 is out of standard support). Move build-publish.yml off the retired ubuntu-20.04 hosted runner to ubuntu-24.04 so the tag build can schedule. Changeset so release-pre can cut v2.20.1-rc.0 for the Data Feeds Tron DON.
The bullseye-security pool returns 404 for jq, so the golang:1.23-bullseye build stages cannot apt-get install and the image build fails before the final stage. Use golang:1.23-bookworm for both build stages. The final image goes to ubuntu:24.04 rather than 22.04 so the cgo node binary built against bookworm's glibc 2.36 is guaranteed to run (24.04 is glibc 2.39, 22.04 is 2.35). 24.04 also matches every current release line and the ca-certificates 20260816ubuntu0.24.04.1 bundle already verified on 10/20.
dlv@latest resolves to v1.27.2, which requires Go 1.25; this branch builds with Go 1.23. v1.24.2 is the version current release lines pin.
install_wasmd: CosmWasm deleted the releases/v0.40.x branch; clone the v0.40.1 tag directly. Unblocks the three required Core Tests jobs at Setup wasmd. contracts/scripts/requirements.txt: binaries.soliditylang.org now returns 403 to the Python-urllib user agent that solc-select 1.0.4 sends, so make generate fails. solc-select 1.2.0 uses requests instead (200). Hash-pinned with its requests dependencies. Unblocks the required Clean Go Tidy & Generate check.
pg_dump releases since August 2025 write \restrict lines with a random key, so the before/after rollback schema comparison in local db reset/preparetest never matches and Setup DB fails in every Core Tests job. Pass a fixed --restrict-key when pg_dump supports it. The dump is only compared against itself and never persisted.
pip in --require-hashes mode only needs the hash of the file it installs, as the existing pycryptodome line already shows. List the py3-none-any wheel for each package instead of every wheel and sdist.
chainchad
previously approved these changes
Oct 21, 2026
release/2.20.1 was cut by hand from v2.20.0, so package.json still read 2.20.0. release-pre reads the release version from package.json on an existing release branch, and the tag build's version-file-bump check and the image version use it too.
cawthorne
approved these changes
Oct 21, 2026
|
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.




Hotfix line for the Data Feeds Tron mainnet DON, which runs a custom build on
chainlink:2.20.0(RANE-5362).release/2.20.1is cut fromv2.20.0.No node runtime changes. Image, CI, and test-tooling changes only.
Image
core/chainlink.Dockerfile,plugins/chainlink.Dockerfile: build stagesgolang:1.23-bullseyetogolang:1.23-bookworm. The bullseye security archive no longer serves packages (jq 404), so the image cannot build on this branch today.ubuntu:20.04toubuntu:24.04. 20.04 is out of standard support and does not getca-certificates 20260816ubuntu0.24.04.1, which drops the compromised eMudhra intermediate CAs. 24.04 rather than 22.04 because the node binary is cgo (wasmvm) and is now linked against bookworm's glibc 2.36; 22.04 ships 2.35.plugins/chainlink.Dockerfile: pin delve to v1.24.2.@latestnow resolves to a release that needs Go 1.25.CI
build-publish.yml:runs-on: ubuntu-20.04toubuntu-24.04. GitHub retired the 20.04 hosted runner, so the tag build could not schedule.tools/ci/install_wasmd: clone thev0.40.1tag directly. CosmWasm deleted thereleases/v0.40.xbranch, which broke Setup wasmd in all three required Core Tests jobs.contracts/scripts/requirements.txt: solc-select 1.0.4 to 1.2.0, plus itsrequestsdependencies, one wheel hash each.binaries.soliditylang.orgnow returns 403 to the Python-urllib user agent 1.0.4 sends; 1.2.0 usesrequests. Fixes the required Clean Go Tidy & Generate check.core/cmd/shell_local.go: backport of Make DB schema dumps deterministic with a restrict key for testing #18985. pg_dump releases since August 2025 write\restrictlines with a random key, so the before/after rollback schema comparison inlocal db preparetestnever matches and Setup DB fails in every Core Tests job. Pass a fixed--restrict-keywhen pg_dump supports it. Only used by thelocal db reset/preparetestCLI; the dump is compared against itself and never persisted.package.json: version 2.20.0 to 2.20.1. The branch was cut by hand fromv2.20.0, so nothing had bumped it; release-pre reads the version from package.json on an existing release branch.v2.20.1-rc.0.Checks
Required on this PR: Clean Go Tidy & Generate, Core Tests (go_core_tests, go_core_tests_integration, go_core_race_tests), test-scripts. Both Build Chainlink Image checks pass. Other red checks are not required and come from tooling drift on a January 2025 branch: verify-version (chain-selectors), goreleaser split jobs, CCIP integration tests, the branch's own push-triggered sigscanner.
After the tag builds, Data Feeds rebuilds the Tron layer on this image (relayer binary copied onto the core image).
Context: #engineering eMudhra CA compromise thread; #proactive-20261020-emudhra-intermediate-ca-compromise.