Repository navigation
chore: force next release to v2.59.0 - #760
Merged
Merged
Conversation
Release-As: 2.59.0 Co-authored-by: Cursor <[email protected]>
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
wesleyboar
added a commit
that referenced
this pull request
Oct 7, 2026
Try #760 again. Release-As: 2.59.0
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
mainChanges
Release-As: 2.59.0footer (per PUBLISHING.md)Testing
main.chore(main): release 2.59.0(not 3.0.0).Notes
Made with Cursor