RepoJournal
AI Red Teaming AI Red Teaming
52 wires and counting

$ follow AI Red Teaming

Keep up with AI Red Teaming in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-11-22
stories 32

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

promptfoo drops Node 23 and 25, PyRIT removes legacy pyrit_scan flags

By RepoJournal · Filed · About AI Red Teaming · Composed from the cited sources · methodology

Both red-teaming CLIs shed legacy surfaces in the same 24 hours: promptfoo narrows its supported Node.js range for Inquirer, and PyRIT 1.3.0 removes the flag-style pyrit_scan invocations and the deprecated converter_ids field.

fix(deps)!: update Inquirer and supported Node.js releases promptfoo/promptfoo

by renovate

promptfoo now requires Node.js ^22.22.2 || ^24.15.0 || >=26, dropping 22.22.0, 22.22.1, Node 23, earlier Node 24 releases and Node 25. This is a breaking change: the install fails on those runtimes, so check your CI image's Node version before pulling the release.

MAINT: Remove the legacy flag-style pyrit_scan invocations microsoft/PyRIT

by khushi-git-7

The legacy flag-style pyrit_scan invocations are gone, as scheduled for 1.3.0: _LEGACY_COMMAND_FLAGS, _warn_legacy and the three legacy rewrites were deleted, and arguments without a verb now exit 2 as a usage error. Scripts must move the subcommand to the front of the command line; the remaining reordering lives in _move_verb_to_front.

MAINT: Remove the deprecated converter_ids field from AddMessageRequest microsoft/PyRIT

by khushi-git-7

AddMessageRequest no longer accepts the deprecated top-level converter_ids field, also due in 1.3.0, and a mode="before" validator now rejects requests that still send it with an HTTP 422 pointing at request_converter_configurations. Old clients fail loudly rather than having their message sent without converters.

FEAT: Generate datasets from a policy in the GUI (-6) microsoft/PyRIT

by richlundeen

Part -6 of the ASSERT stack lands the GUI path for generating datasets from a policy, following the already-merged judge dimensions, OpenTelemetry trace evidence, headline metrics, staged generation and generation jobs PRs.

chore(deps): update dependency jsdom to v31 promptfoo/promptfoo

by renovate

The remaining maintenance is housekeeping: promptfoo's jsdom v31 bump now shares one copy across the site and Web UI workspaces so Vitest can start, and @babel/core moved from 8.1.0 to 8.1.2.

Quick answers

What shipped in AI Red Teaming on November 22, 2026?
Both red-teaming CLIs shed legacy surfaces in the same 24 hours: promptfoo narrows its supported Node.js range for Inquirer, and PyRIT 1.3.0 removes the flag-style pyrit_scan invocations and the deprecated converter_ids field. In total, 9 commits and 23 pull requests landed.
Who contributed to AI Red Teaming on November 22, 2026?
3 developers shipped this update, including renovate, richlundeen, and khushi-git-7.
What were the notable AI Red Teaming updates?
fix(deps)!: update Inquirer and supported Node.js releases, MAINT: Remove the legacy flag-style pyrit_scan invocations, and MAINT: Remove the deprecated converter_ids field from AddMessageRequest.