Skip to content

chore: force next release to v2.59.0 - #760

Merged
wesleyboar merged 1 commit into
mainfrom
chore/release-as-2.59.0
Oct 7, 2026
Merged

wesleyboar merged 1 commit into
mainfrom
chore/release-as-2.59.0

Conversation

@wesleyboar

@wesleyboar wesleyboar commented Oct 7, 2026 •

Copy link
Copy Markdown
Member

Overview

Forces release-please to propose 2.59.0 (minor) instead of 3.0.0 after fix(components)! on #758.

Important

Why? v3 is a whole project. I will update clients to not break by immediately integrating this breaking change for them.

Related

Changes

  • added empty commit with Release-As: 2.59.0 footer (per PUBLISHING.md)

Testing

  1. Merge this PR to main.
  2. Confirm release-please updates chore(main): release 2.59.0 #759 to chore(main): release 2.59.0 (not 3.0.0).

Notes

Made with Cursor

Release-As: 2.59.0
Co-authored-by: Cursor <[email protected]>
@qodo-code-review

Copy link
Copy Markdown

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

@wesleyboar
wesleyboar merged commit 6ebb746 into main Oct 7, 2026
@wesleyboar
wesleyboar deleted the chore/release-as-2.59.0 branch October 7, 2026 19:12
wesleyboar added a commit that referenced this pull request Oct 7, 2026
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.

1 participant