Release v0.11.0

[Paulo Lacerda (placerda)]

Release v0.11.0

Automated release branch created from develop.

What happened

• Branch release/v0.11.0 created from develop
• CHANGELOG.md updated: versioned section [0.11.0] added
• Plugin versions synced to 0.11.0 (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. This is the only verification that runs before PyPI.
2. Review and approve this PR
3. Merge to main
4. Tag and push. This publishes to PyPI immediately, there is no approval step and no undo: git tag v0.11.0 && git push origin v0.11.0
5. Sync develop in the same sitting: git checkout develop && git merge main && git push origin develop
6. Verify the sync: git fetch origin && git log --oneline origin/develop..origin/main must print nothing

Checklist

• Staging pipeline passes (build + TestPyPI + VSIX pre-release + verify)
• CHANGELOG entries reviewed
• PR approved and merged to main
• Tag v0.11.0 pushed (publishes to PyPI, irreversible)
• Release workflow green (PyPI + VSIX stable + GitHub Release)
• develop synced from main: git log --oneline origin/develop..origin/main prints nothing

[Paulo Lacerda (placerda)]

Staging status

Python release validation is green: build/tests passed, TestPyPI publish succeeded, and installation/smoke verification succeeded. The only failing job is publish-vsix-prerelease because repository secret VSCE_PAT contains an expired Azure DevOps Marketplace PAT.

Release is intentionally paused before merge/tag to avoid a partially published v0.11.0. Rotate VSCE_PAT with Marketplace: Manage scope, then rerun failed jobs on staging run https://github.com/Azure/agentops/actions/runs/32529049949. No production tag or PyPI release has been created.