Releases: OpsMx/orca
Releases · OpsMx/orca
tag: v8.31.1_1.30.1-rc8 from branch: 1.30.1_v8.31.1
v8.31.1_1.30.1-rc9 Updating README with brief commit details
tag: 1.28.4_v8.24.4-rc12 from branch: v8.24.4-1.28.4-wu
tag: 1.28.4_v8.24.4-rc11 from branch: v8.24.4-1.28.4-wu
Update Dockerfile
tag: 1.28.4_v8.24.4-rc10 from branch: v8.24.4-1.28.4-wu
Added secrets for nexus repository
tag: v8.31.2_1.30.2-rc4 from branch: 1.30.2_v8.31.2
Update Dockerfile
tag: v8.31.1_1.30.1-rc8 from branch: 1.30.1_v8.31.1-jaeger_app-create
Update Dockerfile
tag: v8.31.1_1.30.1-rc7 from branch: 1.30.1_v8.31.1
1.30.1 v8.31.1 monitor front50 task (#40) * Bugfix added configurable timeout value for MonitorFront50Task * OP-20611: Bugfix added configurable timeout value for save pipeline task timeout
tag: 1.28.4_v8.24.4-rc9 from branch: v8.24.4-1.28.4
added configurable timeout value changes for baking images (#39)
tag: 1.26.6_v2.20.3-rc5 from branch: version-2.20.3-1.26.6
OP-20675 : removed "nulls first" from select query orderBy (#37)
tag: v8.31.2_1.30.2-rc3 from branch: 1.30.2_v8.31.2
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]>