fix: move env under deploy step from under integration tests#5129
Merged
ewaostrowska merged 1 commit intomasterfrom Apr 13, 2026
Merged
fix: move env under deploy step from under integration tests#5129ewaostrowska merged 1 commit intomasterfrom
ewaostrowska merged 1 commit intomasterfrom
Conversation
djankows
approved these changes
Apr 13, 2026
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
2 participants
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.
In the #5119 a new "Verify BOM integration test" step was inserted immediately before the env: block. In YAML env: is scoped to the step it's nested under so it silently migrated from the deploy step to the new BOM step. ./mvnw clean deploy then ran without MAVEN_USERNAME/MAVEN_PASSWORD, causing the 401.
This should be fixed with this PR.