chore(deps): bump scitex-dev pin to >=0.17.8 (stop CI flood)#323
Open
ywatanabe1989 wants to merge 1 commit into
Open
chore(deps): bump scitex-dev pin to >=0.17.8 (stop CI flood)#323ywatanabe1989 wants to merge 1 commit into
ywatanabe1989 wants to merge 1 commit into
Conversation
The umbrella's tests workflow runs `scitex-dev ecosystem audit-umbrella-pins .` on every push + nightly cron. With `scitex-dev==0.17.4` pinned here, CI installs the 0.17.4 binary — which has the pre-0.17.8 strict-error PS-170 behaviour and exits 1 the moment any leaf publishes a newer wheel. Result: ~daily ecosystem CI-red email flood to the operator. scitex-dev 0.17.8 (published 2026-06-09 12:07 UTC) makes PS-170 warn-only by default (`scitex-dev ecosystem audit-umbrella-pins .` prints WARN: + exits 0; `--strict` restores the old fail-on-drift for the release-pipeline pre-publish gate). Bumping the pin to `>=0.17.8` lets CI pick up the new binary and the umbrella's `tests` matrix should turn green on the next run. 3 pin sites updated: [project].dependencies (line 71), [project].optional-dependencies.dev (line 934), and the [linter] optional-deps mount (line 1070). operator-SSoT repo — opening PR, NOT merging.
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
1 participant
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.
Summary
Stops the umbrella's daily CI red-email flood by bumping the
scitex-devpin to pick up the warn-only PS-170 behaviour shipped in scitex-dev 0.17.8 (2026-06-09 12:07 UTC).Root cause: The umbrella's
testsworkflow runsscitex-dev ecosystem audit-umbrella-pins .on every push / nightly cron. Withscitex-dev==0.17.4pinned here, CI installs the 0.17.4 binary — which has the pre-0.17.8 strict-error PS-170 behaviour and exits 1 the moment any leaf publishes a newer wheel ahead of the umbrella's==pin. Result: ~12 ecosystem CI reds in a single morning on 2026-06-09.Fix: Bump to
scitex-dev>=0.17.8in all three pin sites:[project].dependencies(line 71)[project].optional-dependencies.dev(line 934)[linter]optional-deps mount (line 1070)scitex-dev 0.17.8 (ywatanabe1989/scitex-dev#146) made PS-170 warn-only by default:
audit-umbrella-pins .now printsWARN:lines to stderr and exits 0, so an upstream leaf release no longer cascades into red CI. Pass--strictto restore the pre-0.17.8 fail-on-drift behaviour for the release-pipeline pre-publish gate.Test plan
Notes
89b7bdd955534e008fadfe98970d4a7f(proj-scitex-dev → lead, 2026-06-09).