Repository navigation
Conversation
- Synchronize Vermeer with Computer 1.8.0 - Check both release versions in Vermeer CI - Run the check when the Computer POM changes
- Use a GitHub Actions glob for release branches - Run version checks on release branch pushes - Preserve existing workflow path filters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes
Vermeer reports 1.7.0 even though Computer is at 1.8.0. Align its version with the release and check the two declarations in CI.
Master rejects Workers reporting a different version, so deploy matching Master and Worker images together and account for an unavailable interval during the transition.
Validation