Skip to content

Release v0.3.4#223

Merged
placerda merged 2 commits into
mainfrom
release/v0.3.4
Jun 1, 2026
Merged

Release v0.3.4#223
placerda merged 2 commits into
mainfrom
release/v0.3.4

Conversation

@placerda
Copy link
Copy Markdown
Contributor

@placerda placerda commented Jun 1, 2026

Release v0.3.4

Automated release branch created from develop.

What happened

  • Branch release/v0.3.4 created from develop
  • CHANGELOG.md updated: versioned section [0.3.4] added
  • Plugin versions synced to 0.3.4 (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.4 && git push origin v0.3.4
  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.4 pushed
  • PyPI publish approved
  • VSIX stable publish approved
  • develop synced from main

placerda and others added 2 commits June 1, 2026 10:49
…#222)

CONTRIBUTING.md and the env-var docs both state that AZURE_OPENAI_ENDPOINT
is auto-derived from the Foundry project endpoint when absent, but
pipeline/runtime.py::_model_config only read AZURE_OPENAI_ENDPOINT with no
fallback. A fresh workspace created by `agentops init` (which writes
AZURE_AI_FOUNDRY_PROJECT_ENDPOINT but not AZURE_OPENAI_ENDPOINT) therefore
always tripped 'Missing environment variables: AZURE_OPENAI_ENDPOINT' the
first time AI-assisted evaluators tried to run locally.

Adds derive_openai_endpoint_from_project() in utils/azure_endpoints.py that
trims the trailing /api/projects/<name> segment to recover the AI Services
account base URL. _model_config uses it as a fallback, restoring the
documented behavior. The missing-deployment error also now nudges users
toward the Foundry deployments list and the execution: cloud escape hatch
so the next step is obvious without leaving the terminal.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@placerda placerda merged commit e4a03d5 into main Jun 1, 2026
5 checks passed
@placerda placerda deleted the release/v0.3.4 branch June 1, 2026 13:54
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