Skip to content

Comments

Bump version to v2.36.0 for next release cycle#21294

Open
chainlink-release-pusher[bot] wants to merge 2 commits intodevelopfrom
chore/bump-base-branch-2.36.0
Open

Bump version to v2.36.0 for next release cycle#21294
chainlink-release-pusher[bot] wants to merge 2 commits intodevelopfrom
chore/bump-base-branch-2.36.0

Conversation

@chainlink-release-pusher
Copy link
Contributor

Version Bump for Next Release

This PR bumps the version on the base branch to match the release branch.

  • Version: v2.36.0

This change was cherry-picked from the release branch after initializing release v2.36.0.

Changes

  • Cherry-picked version bump commit from release branch
  • Includes updated package.json and CHANGELOG

Note: This ensures that the develop branch is synchronized with the release version, avoiding merge conflicts when the release PR is merged.

@github-actions
Copy link
Contributor

I see you added a changeset file but it does not contain a tag. Please edit 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.

@github-actions
Copy link
Contributor

github-actions bot commented Feb 24, 2026

✅ No conflicts with other open PRs targeting develop

@HashWrangler HashWrangler force-pushed the chore/bump-base-branch-2.36.0 branch from 5e50619 to 59aa1ac Compare February 24, 2026 19:30
@cl-sonarqube-production
Copy link

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

@trunk-io
Copy link

trunk-io bot commented Feb 24, 2026

Static BadgeStatic BadgeStatic BadgeStatic Badge

View Full Report ↗︎Docs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants