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

Refactor how we trigger action on version change #2856

Open
ouziel-slama opened this issue Dec 16, 2024 · 0 comments
Open

Refactor how we trigger action on version change #2856

ouziel-slama opened this issue Dec 16, 2024 · 0 comments
Assignees

Comments

@ouziel-slama
Copy link
Contributor

Currently the system is rigid and depends on major and minor versions. We need a more flexible system where we can trigger a rollback, a reparse and/or a cache clearing of unsupported transactions.
For example:

ACTION_REQUIRED_ON_UPGRADE = {
      ....,
     "v10.8.0": [("rollback", 871780)],
     "v10.9.0": [("reparse", 874000), ("clear_not_supported_cache",)],
     ....,
}

and when we are upgrading from v10.7.0 to v10.9.0 we should only ("rollback", 871780) and ("clear_not_supported_cache",)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants