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

upgrade: fix 2.6 -> 2.7 migration for 2.7.1 patch (#1649) #1708

Merged
merged 4 commits into from
May 2, 2023

Conversation

katexochen
Copy link
Member

Checklist

  • Add labels (e.g., for changelog category)

Also correctly set microservice version from config.
Previously the key was ignored and microservices were always
tried for an upgrade.
This allows us to build a CLI that reports the given version during
an upgrade test. With this we can test patch upgrades.

Signed-off-by: Otto Bittner <[email protected]>
pre-release versions and release versions behaved differently.
This lead to a duplicate v prefix in the cli's version.

Signed-off-by: Otto Bittner <[email protected]>
@katexochen katexochen added the backport This PR is a backport to a previous release label May 2, 2023
@katexochen
Copy link
Member Author

@derpsteb The description of #1649 might need some more polishing for the changelog.

@katexochen katexochen added the bug fix Fixing a bug label May 2, 2023
@katexochen katexochen merged commit 3a92914 into release/v2.7 May 2, 2023
@katexochen katexochen deleted the backport/v2.7/1649 branch May 2, 2023 10:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport This PR is a backport to a previous release bug fix Fixing a bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants