Repository navigation
Flagship package docs are out of date for its next release (CHANGELOG gaps, wrong versions) #4875
Description
The flagship agent's next npm release will ship docs that don't match what it does. The [Unreleased] CHANGELOG leaves out several user-visible fixes and gives two different contract versions. The SKILL.md smoke test shows the wrong agent version. Integrators upgrading can't tell what changed or which contract the release targets.
🔍 Evidence and locations
Severity: 🟠 medium Lens: docs
Auto-fixable: yes — apply bug to let auto-fix open the PR
| Where | Evidence |
|---|---|
hub/agents/gaia/npm/CHANGELOG.md · [Unreleased] |
These commits touch code the flagship bundles but are not in the CHANGELOG: c5c9141 (#4864, line endings preserved on edit), e0fd671 (#4857, a "no" to creating a folder covers writing into it), b448319 (#4809, no forced image), 9dc6b5d (#4827, summaries not cut mid-sentence), 025a7b6 (#4734, owner-password PDFs), 665e3ec (#4754, big documents index in the background), a1dbf09 (#4719). A case-insensitive grep of the section for crlf, line ending, pdf, image and summar finds none of them. |
hub/agents/gaia/npm/CHANGELOG.md · [Unreleased] Notes |
:339 "Tracks sidecar contract apiVersion 2.14", while :250 in the same section says "(contract 2.15)". npm/src/lifecycle.ts:59 and server.py:76 are both "2.15". |
hub/agents/gaia/npm/SKILL.md · Smoke test (curl /version) |
:654 {"apiVersion":"2.15","agentVersion":"0.1.1"}, but gaia_agent/__init__.py __version__ = "0.2.0" and npm/package.json is 0.2.0. |
Not acting on this? Close it with the audit-wontfix label and the audit will never re-file it. Applying bug instead hands it to the existing auto-fix job.
Activity