Skip to content

Bump version to v7.1.0-beta.0 (not a release) #7269

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

Merged
merged 1 commit into from
Apr 7, 2025

Conversation

michaelsproul
Copy link
Member

Proposed Changes

Having merged the drop-headtracker PR we now have a DB schema change in unstable compared to release-v7.0.0:

There is a DB downgrade available, however this needs to be applied manually and it's usually a bit of a hassle.

This PR bumps the version on unstable to v7.1.0-beta.0 without actually cutting a v7.1.0-beta.0 release, so that we can tell at a glance which schema version a node is using.

Additional Info

Our next release with hot tree-states can be v7.1.0 rather than v8.0.0 because we have a schema downgrade for this change as well:

@michaelsproul michaelsproul added ready-for-review The code is ready for review tree-states Ongoing state and database overhaul labels Apr 7, 2025
Copy link
Member

@jimmygchen jimmygchen left a comment

Choose a reason for hiding this comment

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

LGTM!

@michaelsproul
Copy link
Member Author

I'm not sure why that network test failed. Looks a bit sus.

@michaelsproul michaelsproul added ready-for-merge This PR is ready to merge. and removed ready-for-review The code is ready for review labels Apr 7, 2025
@mergify mergify bot merged commit 47a85cd into sigp:unstable Apr 7, 2025
31 checks passed
@michaelsproul michaelsproul deleted the bump-v7.1.0 branch April 7, 2025 06:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-for-merge This PR is ready to merge. tree-states Ongoing state and database overhaul
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants