[GitHub Request] Release agent-health version 0.5.0

[goyamegh]

What is the type of request?

Repository Management

Details of the request

Please cut release v0.5.0 for opensearch-project/agent-health.

• Repo: https://github.com/opensearch-project/agent-health
• Last release: v0.4.0
• Proposed next release: v0.5.0 (minor bump — feature work + fixes since v0.4.0)
• 31 commits on main since v0.4.0; release notes drafted in CHANGELOG.md under [Unreleased].

PRs included since v0.4.0:

Features

• Add link checker #206 feat(skills): skill evaluator with SSE keepalive heartbeat, auto-populated Results / Improvement / History tabs, inline parse errors, and accurate startup config log
• #207 feat: code-based test case SDK with Playwright-style test() API
• Fix onboarding link in README #205 feat: add Pi.dev connector, EvaluationRun architecture, and evals3 fixes
• Move COMMUNICATIONS file to community repo #212 feat(traces): inline-expand trace rows, plain-text service, relative start time
• Replace contact information in code-of-conduct, potentially replace the CoC itself.  #217 feat(traces): fullscreen parity with inline expansion (timeline bars + summary strip)
• #211 feat: pre-populate Observio in test-case popup and unify preferences across sidebar pages
• [PROPOSAL] Tools for Collaborating on Design/Proposal Generation #181 feat(observio): port auto-increment and configurable max iterations
• Updating the admin list #191 feat(overview): rewrite First Run Experience as narrative landing
• Updated the admins list #189 feat: enforce high coverage standards on PRs with ratchet and patch gates
• [META/Proposal] OpenSearch project should Adopt Apache Foundation's stance on the use of genAI #182 feat: hide sample data and collapse built-in agents when custom data exists
• [ENHANCEMENT] Improve untriaged label workflow to ignore issues created by maintainers #157 feat: Add Claude Code Judge evaluator and AI Assistant chat interface

Fixes

• [PROPOSAL] transfer opensearch-mock to opensearch organization #224 fix: judge fail-fast on validation errors and show error status in UI
• Update RESPONSIBILITIES.md #223 fix(e2e): make code-SDK trace polling and Observio specs not hang in CI
• Updates to README, profile, & ONBOARDING files #213 fix(settings): test-connection reads stored credentials from config file
• Added proposing features. #210 fix: observio startup race condition and telemetry visibility
• #214 fix(ui): unify sidebar background and apply gradient to all pages
• [PROPOSAL] Document a clear(er) bar/process for moving repos into opensearch-project #209 fix(security): address Mend dependency vulnerabilities (#162, #163, #201, #202, #203, #208)
• Added information on attending triage meetings. #200 fix: useTraces: true blocks benchmark runner until judge evaluates (#184)
• #197 fix: add SSE disconnect recovery and polling fallback for ad-hoc evaluations
• Introducing "Maintainers in Training" program to introduce new maintainers #195 fix(e2e): resolve all pre-existing E2E test failures and add gate job
• Updating security reachout email #204 fix: add EVAL category capsule to span viewer UI
• Updating the admin list #193 fix: resolve Dependabot security vulnerabilities via npm overrides
• [PROPOSAL] Document current security mechanisms #172 fix: resolve 6 papercut issues (#166–#171)
• Clarity around "untriaged" issue handling #176 fix: use single source of truth for connector types

CI / chore

• #221 Pin actions/github-script to exact commit SHA
• Updating security reachout email #199 Add GitHub environment to release workflow

Dependency bumps

• Clarifying "experimental features" in OpenSearch [DISCUS][BUG] #178, [PROPOSAL] Build a GitHub app / workflow that runs on each PR that modifies the CODEOWNERS and MAINTAINERS files to make sure they are in sync #177, #175, Documented admin permissions for adding maintainers and creating repos. #174, [PROPOSAL] Clarify Issue Types and "Last Call for Comments" #164

Additional information to support your request

• Maintainers of agent-health have driven the changes above and reviewed the changelog; this issue is the standard [GitHub Request] to schedule the org-side release tag/publish step.
• npm-publish.yml workflow is wired to publish to npm on a v* tag push; we will bump package.json from 0.4.0 → 0.5.0, move [Unreleased] notes under ## [0.5.0] - <date>, and push tag v0.5.0.
• After publish we'll verify npx @opensearch-project/agent-health@0.5.0 doctor and draft the GitHub Release with the same notes.

When does this request need to be completed?

Soon — we'd like to ship 0.5.0 this release window so downstream consumers can pick up the skill evaluator (#206), code-based test SDK (#207), and other paper cuts.

Notes

Track the progress of your request here: Engineering Effectiveness Board (view).
Member of @opensearch-project/admin will take a look at the request soon.
Thanks!

[peterzhuamazon]

Hi @goyamegh from which commit of which branch you want to create v0.5.0.

Thanks.