tag: v8.31.2_1.30.2-rc3 from branch: 1.30.2_v8.31.2
·
1 commit
to 1.30.2_v8.31.2
since this release
fix(queue): Manual Judgment propagation (#4475) (#36)
Manual Judgment was always propagated if the MJ stage was the first one in the pipeline, regardless of the value of `propagateAuthenticationContext`.
The code for backtracking through stages to find an `AuthenticatedStage` provider would improperly return any stage that did not have an ancestor, ignoring criteria for selecting a stage that should be propagating authentication.
Additionally, code in `AuthenticationAware` would mutate a `SKIPPED` MJ stage, copying the `LastModifiedDetails` value from the "real" MJ stage ancestor (or the root stage, as described above). This mutation is not necessary, and `AuthenticationAware` can just ignore it as it traverses ancestors of the current stage.
Co-authored-by: jcavanagh <[email protected]>