Chainlink, the leading decentralized oracle network, has released version 2.66.0, bringing a mix of breaking, minor, and patch changes that affect node operators and developers alike.
The most significant change is the upgrade of the minimum supported PostgreSQL version from 14 to 15. Nodes that continue to run PostgreSQL 12, 13, or 14 will no longer start, and operators must migrate their databases before applying the new node image. While the SKIP_PG_VERSION_CHECK environment variable can bypass the check, it is explicitly marked as unsupported and should only be used for testing or in environments where the database is already end‑of‑life.
Beyond the database shift, the release includes a minor version bump and several patches. The deprecated Cosmos support has been removed, simplifying the codebase and reducing maintenance overhead. Additionally, a new bridge‑cache fallback has been introduced for UseConnectionManager bridge tasks, improving reliability when external connections are temporarily unavailable.
Chainlink operators can pull the updated image from DockerHub or Amazon ECR using the provided digests. Verification instructions are included, allowing users to confirm the authenticity of the image with cosign and GitHub workflow certificates.
Full details of the changelog, including pull request references and diff links, are available on GitHub. The release underscores Chainlink’s commitment to security, performance, and developer experience while encouraging operators to keep their infrastructure up to date.
For those maintaining production nodes, the PostgreSQL upgrade is the most urgent action. The other changes, while less disruptive, still represent important improvements to the network’s resilience and code quality.
Overall, v2.66.0 delivers a cleaner, more secure foundation for Chainlink’s oracle services, ensuring that the network remains robust as it scales.