Chainlink’s latest release, v2.65.0, went live on September 21, 2026, bringing a set of refinements that improve observability for confidential‑workflow enclaves and streamline image distribution. The update is positioned as a maintenance release, but its changes target a critical pain point for developers building secure data pipelines.
The release begins with a minor version bump, a standard practice that signals a non‑breaking update while preparing the codebase for the next major iteration. The change is straightforward, but it underscores Chainlink’s commitment to clear versioning and backward compatibility.
A more substantive patch introduces a new label to the `enclave_execution_failures` counter. By tagging each failure with an `error_type` of either "user" or "system", the system can now filter alerts to exclude failures caused by user‑side misconfigurations, such as exceeding an enclave’s execution budget. This granularity helps operators focus on genuine infrastructure issues and reduces noise in monitoring dashboards.
Container images for the new release are published to both DockerHub and Amazon ECR, with a SHA‑256 digest (`4beb2f0759f1ce77e175f9a54685263deaa3ad462dd593fd79d4cd9d3ee147b4`) that can be verified using cosign. The verification steps, which include certificate checks against GitHub Actions workflows, provide an additional layer of security for deployments.
Developers can explore the full list of changes in the official changelog or compare the new release against v2.64.0 to assess the impact on their deployments. The update’s focus on enclave failure labeling and image security positions Chainlink to better support confidential workflows in production environments.