Repository navigation
ci: add clean-env-from-lock input for repos with unpublished git dependencies - #2
Merged
Merged
Conversation
…ndencies The clean-env install step resolves from PyPI, which fails while engg-math packages are only available as git sources. With the input set, the locked runtime set is installed first. The audit job already supports skipping packages through export-args.
export-args omits git-sourced packages for pip-audit; the clean env needs them.
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.
The build job's clean-env step installs the wheel from PyPI, so any repo depending on a not-yet-published engg-math package fails there (engg-math-linear-systems, run 41975900230).
clean-env-from-lock(defaultfalse): exports the locked runtime set withuv export --locked --no-dev --no-hashesand installs it into the clean env before the wheel.export-args: --no-emit-package <pkg>for git-sourced packages, since pip-audit cannot hash them.Callers drop both settings once the infrastructure packages are on PyPI (Phase 6).