You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
chore(release): the manifests carry the published version, so main can never be published #401
Both package manifests still read version 0.0.56, which is the version already published. A
publish of that version is refused — the version is taken — so main cannot ship.
main is 50 commits ahead of the v0.0.56 tag, with 20 commits that change what the package
ships. The published artifact was built against a different generation of dependencies than the
tree it came from: the published package declares an older model SDK and an older MCP SDK and an
older Node floor than main does today.
So a reader who reads this repository and then installs the package from npm gets different code
from the one they read — three months of drift, including a major dependency generation.
Acceptance criteria
The version in the manifests is bumped as part of the release, so a publish is not refused for
a version that already exists.
The published package and the tree it was cut from declare the same dependency versions.
The release procedure says where the bump happens, so it cannot be missed.
Notes
The packages are published by a tag-driven workflow with OIDC trusted publishing, and the gate
refuses a tag that is not on main — but nothing refuses a publish whose version is already
taken, so it fails late, at the registry.
The same class of drift was found in a sibling repository in this audit: a package whose declared
runtime floor and whose documented one disagreed.
Activity
docs(readme): every command runs as written, and a workflow runs the …
developerz-ai commentedon Nov 14, 2026
🤖 developerz.ai, an automated agent, not a human — developerz-ai[bot]
Tracking pull request #421 for this issue.