[GitHub Request] Create release tag 0.6.0 for agent-health

[goyamegh]

What is the type of request?

Repository Management

Details of the request

Requesting creation of the git tag 0.6.0 for opensearch-project/agent-health.

• repository: https://github.com/opensearch-project/agent-health
• target branch: main
• required tag: 0.6.0 (no v prefix, per this repo's RELEASING.md convention)
• commit to tag: a33c5a9d4e45853668b2caf20d48ebdbc3ff1dbe
  (opensearch-project/agent-health@a33c5a9 — "chore: release 0.6.0 ([GitHub Request] Add user andrewmains12 to TSDB project #436)", the version-bump PR that bumped package.json/package-lock.json 0.5.2 → 0.6.0 and rolled the CHANGELOG)
• previous tag: 0.5.2

Equivalent command:

git tag -a 0.6.0 a33c5a9d4e45853668b2caf20d48ebdbc3ff1dbe -m "Release 0.6.0"
git push origin 0.6.0

The release is prepared and verified: PR #436 (version bump + CHANGELOG) is merged into main, CI (build/test on Node 18/20/22, integration tests, lint/typecheck) was green on the merge commit, and npm audit --audit-level=high reports no high/critical vulnerabilities.

Repo maintainers have maintain (not admin), so the org-level tag ruleset blocks tag creation via git push for everyone except org admins.

Additional information to support your request

• I am a repo maintainer (goyamegh) raising this per the "contact the corresponding maintainers before raising the issue" note; maintainers TackAdam, ps48, and jasonlhamazon are aware.
• Pushing the tag triggers this repo's Release Workflow (build/test/publish); a maintainer will still need to approve the release-approval environment gate in Actions afterward before anything publishes to npm.
• This blocker recurs on every agent-health release (see [GitHub Request] Create release tag 3.8.0.0 for opensearch-prometheus-exporter #627 for the same ask on a different repo, and prior agent-health tag requests handled via direct Slack pings to org admins). It would be worth revisiting whether repo maintainers can be granted tag-creation bypass on this repo to avoid a repeat "GitHub Request" issue every release cycle.

When does this request need to be completed?

Soon — the version bump is merged and verified; requesting this be picked up within the standard 7-10 business day window, sooner if possible since users are waiting on the 0.6.0 npm release.

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]

Duplicate with #640