Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Downgrade version number #10157

Merged
merged 1 commit into from
Jan 14, 2025
Merged

Downgrade version number #10157

merged 1 commit into from
Jan 14, 2025

Conversation

mcleinman
Copy link
Collaborator

We're going to re-cut a new 2.25.0 release branch (likely later this week). While we could wait until the release branch is cut and then do a similar PR against the release branch, doing it against main (this PR) means we're not blocked on PR approvals and our lengthy tests during the release process. (After the release branch is cut, I'll put up a PR to revert this to 2.26.0 on main.)

@mcleinman mcleinman requested a review from oskirby December 30, 2024 23:05
Copy link
Collaborator

@oskirby oskirby left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have a sneaking suspicion this might cause some funky breakage in CI, but it'll be transient so this should be okay.

@mcleinman
Copy link
Collaborator Author

I'm going to wait and merge this right before I create the new branch - thus we won't terrible break CI tests for other PRs coming in this week.

@mcleinman mcleinman changed the base branch from main to releases/2.25.0 January 14, 2025 18:41
@mcleinman mcleinman merged commit b288fdb into releases/2.25.0 Jan 14, 2025
115 of 117 checks passed
@mcleinman mcleinman deleted the version_downgrade branch January 14, 2025 18:41
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