Skip to content

Commit 563551a

Browse files
slister1001Copilot
andauthored
[evaluation] backport 1.16.6 release notes; bump version to 1.16.7 (#46574)
- Set 1.16.6 release date to 2026-04-27 (matches PyPI release) - Add #46502 token usage bullet to 1.16.6 (shipped in hotfix) - Add empty 1.16.7 (Unreleased) section - Bump _version.py to 1.16.7 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
1 parent d0e5502 commit 563551a

3 files changed

Lines changed: 11 additions & 3 deletions

File tree

sdk/evaluation/azure-ai-evaluation/CHANGELOG.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,20 @@
11
# Release History
22

3-
## 1.16.6 (Unreleased)
3+
## 1.16.7 (Unreleased)
44

55
### Features Added
66

77
### Breaking Changes
88

99
### Bugs Fixed
1010

11+
### Other Changes
12+
13+
## 1.16.6 (2026-04-27)
14+
15+
### Bugs Fixed
16+
17+
- Fixed evaluation token usage not being emitted in the genai evaluation event, causing token consumption metrics to be missing from telemetry.
1118
- Fixed multi-turn red team attacks (`RedTeamingAttack`-based strategies like `MultiTurn`) failing silently with PyRIT 0.11. Two bugs were patched at the SDK level: (1) `RedTeamingAttack._setup_async` raised `RuntimeError: Conversation already exists` because it seeded prepended conversation messages before calling `set_system_prompt`; now patched per-instance on the adversarial chat target to tolerate existing conversation history. (2) `RedTeamingAttack._generate_next_prompt_async` returned `context.next_message` without calling `.duplicate_message()`, causing `sqlite3.IntegrityError: UNIQUE constraint failed: PromptMemoryEntries.id` on the second turn; now patched at module load with an idempotent wrapper that duplicates the message before returning.
1219
- Fixed `sensitive_data_leakage` red team attacks producing 100% false-pass rates. `_extract_context_items` in the Foundry execution path only handled `list` or `dict` shapes for `messages[0].context`; pre-curated SDL attack objectives store the document text as a `str` with sibling `context_type`/`tool_name` fields, so the document was silently dropped and a fallback synthesized a context item from the user prompt. The agent never received the sensitive document content and could not leak it, causing the evaluator to score every attempt as a pass. Added `str` handling (both message-level and top-level), normalized raw string entries inside list-shaped context, and gated the `context_type` fallback so it only runs when no usable context was extracted (including the `context: null` case).
1320

sdk/evaluation/azure-ai-evaluation/azure/ai/evaluation/_version.py

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,4 +3,4 @@
33
# ---------------------------------------------------------
44
# represents upcoming version
55

6-
VERSION = "1.16.6"
6+
VERSION = "1.16.7"

sdk/evaluation/azure-ai-evaluation/cspell.json

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,8 @@
3131
"etests",
3232
"redteam",
3333
"redef",
34-
"smode"
34+
"smode",
35+
"genai"
3536
],
3637
"ignorePaths": [
3738
"sdk/evaluation/azure-ai-evaluation/azure/ai/evaluation/_common/onedp/models/_enums.py",

0 commit comments

Comments
 (0)