Skip to content

feat(upgrade): specify upgrade starting version constraint #603

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

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

Frostman
Copy link
Member

@Frostman Frostman commented May 9, 2025

No description provided.

@Frostman Frostman requested a review from a team as a code owner May 9, 2025 05:04
@Frostman Frostman force-pushed the dev/frostman/upgrade-check branch from c8cc946 to 5256ba7 Compare May 9, 2025 05:10
@Frostman Frostman requested a review from a team as a code owner May 9, 2025 05:10
Frostman added 2 commits May 8, 2025 23:05
Signed-off-by: Sergei Lukianov <me@slukjanov.name>
Signed-off-by: Sergei Lukianov <me@slukjanov.name>
@Frostman Frostman force-pushed the dev/frostman/upgrade-check branch from 5256ba7 to ae4f278 Compare May 9, 2025 06:08
@Frostman Frostman marked this pull request as draft May 9, 2025 06:08
@Frostman
Copy link
Member Author

Frostman commented May 9, 2025

It's not working correctly due to the issue with the fabricator status versions calculation which shouldn't be touched in some cases like reading one before the upgrade but then it should get an override when we're applying the upgrade

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

Successfully merging this pull request may close these issues.

1 participant