Skip to content

Release v0.3.18#292

Merged
placerda merged 4 commits into
mainfrom
release/v0.3.18
Jun 10, 2026
Merged

Release v0.3.18#292
placerda merged 4 commits into
mainfrom
release/v0.3.18

Conversation

@placerda

Copy link
Copy Markdown
Contributor

Release v0.3.18

Automated release branch created from develop.

What happened

  • Branch release/v0.3.18 created from develop
  • CHANGELOG.md updated: versioned section [0.3.18] added
  • Plugin versions synced to 0.3.18 (package.json, plugin.json, marketplace.json)
  • Staging pipeline triggered automatically (build → TestPyPI + VSIX pre-release → verify)

Next steps

  1. Wait for the Staging pipeline to pass
  2. Review and approve this PR
  3. Merge to main
  4. Tag and push: git tag v0.3.18 && git push origin v0.3.18
  5. Approve the PyPI publish and VSIX stable publish in the Release workflow
  6. Sync develop: git checkout develop && git merge main && git push origin develop

Checklist

  • Staging pipeline passes (build + TestPyPI + VSIX pre-release + verify)
  • CHANGELOG entries reviewed
  • PR approved and merged to main
  • Tag v0.3.18 pushed
  • PyPI publish approved
  • VSIX stable publish approved
  • develop synced from main

placerda and others added 4 commits June 9, 2026 16:51
)

Step 10 (Check the selected eval runner) was a 387-line wall covering
azd recipe init, smoke gate, multi-turn upgrade, optional Foundry full
conversations, rubric creation, ASSERT runner, Red Team runner, and the
evidence pack pull-in. Readers were dropping off mid-step.

Split into three focused steps without changing any technical content
or removing the optional multi-turn / Foundry portal path:

- Step 10: Initialize the azd eval recipe and run the smoke gate.
- Step 11: Harden the gate with the conversation-aware dataset and the
  Travel Agent rubric. Keeps the 'Optional: Full conversations in the
  Foundry portal' subsection.
- Step 12: Add ASSERT and Red Team to the release gate (absorbs the
  former 10a/10b/10c subsections, including the evidence pack pull-in).

Renumber sections 11..18 to 13..20 and update 9 internal cross-references
('in step 13' to 'in step 15', 'in step 16' to 'in step 18', 'workflows
in step 11' to 'workflows in step 13', 'in step 12' to 'in step 14',
'baseline run in step 13' to 'baseline run in step 15').

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…tart (#290)

Replace 'open-source framework and CLI' with 'open-source AgentOps
jumpstart' in the README badge subtitle and Overview. Framework implied
something users had to inherit from or build inside, which AgentOps is
not — it orchestrates external tools (Foundry Evaluations, ASSERT,
PyRIT, Azure Monitor, azd) and ships normalized evidence.

Also add 'observability' to the activity list so the descriptor reflects
that AgentOps surfaces App Insights production telemetry through the
Cockpit and Doctor, not just release-gate evaluation.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
When `execution: azd` fails, `agentops eval run` previously bubbled up only the active azd spinner line (e.g. `Resolving eval context...`), giving users no actionable diagnostic. The runner now includes the full command, exit code, and both stderr and stdout in the error, and persists raw streams to `.agentops/results/<ts>/azd_eval_run_{stdout,stderr}.log` (plus matching `azd_eval_show_*` files when the show step fails).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@placerda placerda merged commit b823d78 into main Jun 10, 2026
5 checks passed
@placerda placerda deleted the release/v0.3.18 branch June 10, 2026 11:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant