ci: generate and validate dependency repair candidates - #22
Draft
ArjiaTechnologies wants to merge 9 commits into
Draft
ArjiaTechnologies wants to merge 9 commits into
ArjiaTechnologies wants to merge 9 commits into
Conversation
ArjiaTechnologies
marked this pull request as ready for review
August 15, 2026 19:03
ArjiaTechnologies
marked this pull request as draft
August 16, 2026 03:37
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
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
Provides a read-only, source-bound dependency-lock candidate workflow that is self-validating on this same-repository draft PR.
The workflow now:
mlflowdependency only inside the runner workspace withmlflow-skinny>=3.15.1,<4mlflowdistribution to be absentcontents: read; it cannot commit, push, merge, release, deploy, or mutate productionSuccessful source-bound evidence
Run 32161399841, bound to source SHA
c559110b7c4f6c8d15168d7765a3f81e91fb7b48, completed successfully without a dependency override.Its PyPI-only artifact resolved:
Every generator gate passed: targeted resolution, exact distribution/version invariants, sync,
uv pip check, AES-GCM, SQLite tracking through the skinny-providedmlflownamespace, complete non-ML checks, package/Twine/installed-wheel smoke, Cryptography floor enforcement, andpip-auditwith tracking installed.The reviewed artifact changed only
pyproject.tomlanduv.lock, used only the expected editable ARES self-source plus PyPI, introduced no package, Git/path dependency, alternate registry, or unexplained upgrade, and removed the unused full-MLflow/server dependency closure. It was applied to draft repair PR #23, whose normal CI is fully green at67a94f129eb09ad77cc3ca34b190bba263a11958.Safety
This support PR remains draft and contains only non-production maintenance tooling. It does not include the product dependency repair itself, bypass checks, merge, release, deploy, publish, or change credentials, accounts, production, or branch protection.