Require wait_for_stage parameter for Nexus Workflow Updates - #1883
Merged
Merged
Conversation
|
|
|
|
tconley1428
reviewed
Sep 17, 2026
atol
force-pushed
the
alicelin/NEXUS-765/wait-for-stage
branch
from
September 29, 2026 19:58
69e418b to
004f0c5
Compare
VegetarianOrc
approved these changes
Oct 1, 2026
Contributor
|
Changelog needs to be corrected as it is in the wrong release. |
atol
force-pushed
the
alicelin/NEXUS-765/wait-for-stage
branch
from
October 1, 2026 20:38
11d84ef to
ebca39f
Compare
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
4 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.
What was changed
Expose and require the
wait_for_stageparameter to be explicitly set toACCEPTEDfor Nexus Workflow Updates, instead of being hardcoded internally.Why?
wait_for_stageis expected to be a required parameter becauseACCEPTEDis a non-obvious default that users should be aware of. This also aligns with the behaviour in the Go, Java, and .NET SDKs.How was this tested
Add new test.