[blackice] Move PyRIT install to microsoft/PyRIT with proxy support#250
Merged
gillespeiffer-db merged 2 commits intoJun 5, 2026
Merged
Conversation
PyRIT moved from Azure/PyRIT to microsoft/PyRIT. The old repository is archived and no longer carries the v0.10.0rc0 tag, so checking out that ref during the blackice image build fails. Update the GIT_TOOLS entry to the current upstream and move from the release candidate to the latest stable release v0.13.0.
gillespeiffer-db
force-pushed
the
gpeiffer/blackice-pyrit-microsoft-master
branch
from
bcad47f to
db1dfc1
Compare
madsager-db
reviewed
Jun 4, 2026
gillespeiffer-db
changed the title
gillespeiffer-db
changed the title
madsager-db
approved these changes
Jun 5, 2026
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
2 participants
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
Follow Lasse's package-index proxy pattern from #244 and keep the BlackIce PyRIT version pinned at
v0.10.0rc0while moving from the archivedAzure/PyRITrepo tomicrosoft/PyRIT.Details
The version intentionally stays the same. Testing
v0.13.0built successfully, but it broke the existing BlackIce PyRIT integration because the PyRIT APIs used by our patches changed.This PR:
https://github.com/microsoft/PyRIT.gitv0.10.0rc0Validation
Validated on the 17.3-LTS branch with a fresh no-cache Docker build using internal PyPI, npm, and PyTorch proxies. The BlackIce test suite result was
137 passed, 1 failed; the remaining failure is an unrelatedlm-eval-harness/transformers.AutoModelForVision2Seqcompatibility issue that reproduces independently of the PyRIT version.