$ the-wire · showcase
PyRIT lands saved registry recipes in four parts
By RepoJournal · Filed · About AI Red Teaming · Composed from the cited sources · methodology
PyRIT's registry work landed as a four-part change that lets operators persist recipes and rebuild them at startup, while promptfoo's day was entirely dependency bumps.
FEAT: Read saved registry recipes (part 2) microsoft/PyRIT
PyRIT can now read recipes previously saved from the registry, the second of four parts landing together, so a recipe you configure once survives past the session instead of being rebuilt by hand.
FEAT: Rebuild saved registry entries in dependency order (part 3) microsoft/PyRIT
Saved registry entries rebuild in dependency order, which matters because a recipe that references other registry objects will not restore correctly if its dependencies are reconstructed out of sequence.
FEAT: Restore saved registry entries at startup and stay not ready if any fail (part 4) microsoft/PyRIT
The fourth part restores saved registry entries at startup and keeps PyRIT in a not-ready state if any of them fail to restore, so a broken saved recipe surfaces as an unavailable service rather than a silently partial registry. Upgrade only once all four parts are in the release you run; part one, reporting documents a storage listing cannot use, is the read-side half of the same effort.
TEST: Add ReferenceField component tests microsoft/PyRIT
ReferenceField picks up component tests covering the N. name rows and what onChange receives, in a change the pull request states contains no production code changes. Nothing here alters operator behavior.
chore(deps): update vitest to v5.1.0 promptfoo/promptfoo
The label long tail was all Renovate: vitest and @vitest/coverage-v8 to 5.1.0, oxc-parser to ^0.157.0, @anthropic-ai/claude-agent-sdk to 0.3.317, and @babel/core from 8.0.10 to 8.1.0.