fix(release): verify npm latest across npm 12 output changes

[777genius]

Fix the public registry verifier after the successful 0.1.4 publication.

npm 12 returns npm view <package> dist-tags --json as a singleton array, while npm 11 returns an object. The old jq expression therefore waited for all 30 retries even though 0.1.4 and the latest tag were public.

This checks <package>@latest version as a scalar instead. It proves the same invariant without depending on npm JSON response shape.

Verification:

• targeted release contract test passes
• exact npm 12.0.2 registry query returns 0.1.4
• no publication or lifecycle behavior changes

Summary by CodeRabbit

• Bug Fixes

  • Improved package publication verification to more reliably confirm that the latest released version is available before publication is considered complete.

• Tests

  • Updated release verification checks to validate the latest version directly and maintain accurate ordering expectations.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 8493275d-1f2d-4e80-9725-4ba2050c1d39

📥 Commits

Reviewing files that changed from the base of the PR and between cb1fd2d and 6fc725a.

📒 Files selected for processing (2)

• .github/workflows/agentplugins-npm-publish.yml
• repotests/agentplugins_release_contract_test.go

---

📝 Walkthrough

Walkthrough

The npm publish verification now queries the package’s latest version directly. Contract tests validate this query and require it before exact-version installation.

Changes

Npm latest verification

Layer / File(s)	Summary
Direct latest version check .github/workflows/agentplugins-npm-publish.yml, repotests/agentplugins_release_contract_test.go	The workflow queries latest directly and requires it to match the release version. Contract tests validate the direct query and its ordering before exact-version installation.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• 777genius/plugin-kit-ai#36: Modifies npm publish registry and distribution-tag verification.
• 777genius/plugin-kit-ai#39: Updates npm latest verification in the workflow and contract tests.
• 777genius/plugin-kit-ai#41: Introduces the npm registry propagation checks updated here.

Poem

A rabbit checks the latest tag,
No JSON trails remain.
The release hops to matching code,
While tests confirm the chain.
One direct query, neat and bright—
Version verified right!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the release verification fix for npm 12 output changes.
Description check	✅ Passed	The description explains what and why, lists focused verification, and states release impact; it omits the template headings and checklist format.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/npm12-dist-tag-verification

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}