Release 2.36.0

[chainlink-release-pusher]

Release 2.36.0

Source Ref: develop
Release Tag: v2.36.0-beta.0
Phase: beta

This PR tracks the release process for version 2.36.0.

📌 Merge After Finalization

This PR should be merged after the final release is published to bring release changes back to trunk.

Checklist

• Version bumped via changeset
• Release branch created
• Pre-release tag (beta) created and pushed
• Changeset created for next release
• Testing completed
• Final release tag created

[github-actions]

✅ No conflicts with other open PRs targeting develop

[chainlink-release-pusher]

🚀 New pre-release created (rc): v2.36.0-rc.0

[trunk-io]

     

View Full Report ↗︎ ⋅ Docs

[github-actions]

I see you updated files related to core. Please run make gocs in the root directory to add a changeset as well as in the text include at least one of the following tags:

• #added For any new functionality added.
• #breaking_change For any functionality that requires manual action for the node to boot.
• #bugfix For bug fixes.
• #changed For any change to the existing functionality.
• #db_update For any feature that introduces updates to database schema.
• #deprecation_notice For any upcoming deprecation functionality.
• #internal For changesets that need to be excluded from the final changelog.
• #nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
• #removed For any functionality/config that is removed.
• #updated For any functionality that is updated.
• #wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.

[cl-sonarqube-production]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube