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

Next breaking release #2688

Closed
cwgoes opened this issue Feb 21, 2024 · 6 comments
Closed

Next breaking release #2688

cwgoes opened this issue Feb 21, 2024 · 6 comments

Comments

@cwgoes
Copy link
Collaborator

cwgoes commented Feb 21, 2024

The next breaking should contain ONLY:

Projected for 0.32.X:

@brentstone
Copy link
Collaborator

Wondering if we should also include at least #2617 too.

@cwgoes
Copy link
Collaborator Author

cwgoes commented Feb 22, 2024

Wondering if we should also include at least #2617 too.

We should include it soon, but we want to make this breaking release an automatic upgrade, and my understanding of #2617 is that an automatic upgrade will be somewhat tricky (e.g. we have to update all the current vp_users). What do you think?

@adrianbrink
Copy link
Member

Do we already have the migration code for all the PRs?

@tzemanovic
Copy link
Member

added #2604 that doesn't require migration

@tzemanovic
Copy link
Member

Do we already have the migration code for all the PRs?

we don't have any migration code afaik

@cwgoes
Copy link
Collaborator Author

cwgoes commented Feb 28, 2024

#2617 to be added if possible - @brentstone to investigate state migration options.

This was referenced Mar 4, 2024
@cwgoes cwgoes closed this as completed May 24, 2024
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

No branches or pull requests

4 participants