Chainlink Releases Node v2.65.0 With Confidential Workflow Monitoring Fix

TL;DR Chainlink has published core node software v2.65.0. The release includes a monitoring change that separates user-caused confidential-workflow enclave failures from system-caused failures. It is an infrastructure maintenance release rather than a new Chainlink product launch. Chainlink has pushed out core node software v2.65.0, giving operators another incremental infrastructure update only days after the previous release cycle. The new build is not a headline CCIP launch or a new oracle product. Instead, it focuses on the sort of operational detail that matters to teams running production Chainlink infrastructure. Confidential Workflow Monitoring Gets More Precise One of the key changes in v2.65.0 affects monitoring around confidential-workflow enclave failures. The release adds an `error_type` label to the relevant failure counter, allowing node operators to distinguish between failures caused by user workflows and failures caused by the system itself. That sounds small, but it is useful operationally. If a workflow exceeds its enclave execution budget, operators do not necessarily want the same alerting path they would use for an infrastructure fault. Separating those fail…

≈