Prepare 0.27.7 release

[mohanagy]

Summary

• promote the main branch from 0.27.7-next.1 to stable 0.27.7 metadata
• update the changelog, README release copy, and MCP registry manifest for the stable release
• extend release hygiene so branch-sensitive README docs must point at main for stable releases and next for prereleases

Verification

• npm run test:run -- tests/unit/release-hygiene.test.ts
• npm install
• npm run release:verify
• npm run registry:validate
• npm run typecheck
• npm run build
• CI=1 npm run test:run
• npm pack --dry-run
• npm sbom --sbom-format cyclonedx > sbom.cdx.json

Summary by CodeRabbit

• Chores

  • Version promoted from 0.27.7-next.1 to 0.27.7 across package and registry files.
  • Updated changelog and README with stable release information.
  • Corrected documentation links to target the appropriate release branch.
  • Enhanced release validation to verify correct documentation branching.

• Tests

  • Updated release hygiene test expectations.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 4563d7b5-e1c9-4a23-b797-885e336943e4

📥 Commits

Reviewing files that changed from the base of the PR and between 641672b and ff9c616.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (6)

• .github/scripts/verify-release-hygiene.mjs
• CHANGELOG.md
• README.md
• docs/mcp-registry/server.json
• package.json
• tests/unit/release-hygiene.test.ts

---

📝 Walkthrough

Walkthrough

This PR releases version 0.27.7 by promoting the prerelease 0.27.7-next.1 to stable. It refactors the release-hygiene validation script to generalize README documentation link branch checking from prerelease-only rules to a release-sensitive framework that validates links against the correct GitHub branch (main or next) based on version channel. Version identifiers, release notes, and documentation links are updated across package manifests and user-facing docs.

Changes

Release 0.27.7 promotion

Layer / File(s)	Summary
Release-hygiene validation refactor and test updates .github/scripts/verify-release-hygiene.mjs, tests/unit/release-hygiene.test.ts	Introduces RELEASE_BRANCHED_README_PATHS constant to enumerate release-sensitive documentation paths. Replaces prerelease-specific assertNextOnlyReadmeLinks with generalized assertReleaseBranchedReadmeLinks function that validates GitHub link targets match the expected branch (blob/next for prerelease, blob/main for stable). Updates main() to call the new assertion and modifies test expectations from "next-only" to "release-sensitive" terminology while validating correct branch targets.
Version bump and release notes package.json, CHANGELOG.md, README.md, docs/mcp-registry/server.json	Increments package.json version from 0.27.7-next.1 to 0.27.7. Promotes prerelease CHANGELOG entries into new ## [0.27.7] - 2026-06-02 release section with Added, Changed, and Fixed subsections. Updates README release-notes heading and adjusts documentation links from blob/next to blob/main in the "Documentation & receipts" section. Aligns MCP registry server metadata version to 0.27.7.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

• mohanagy/madar#462: Both PRs modify the release-hygiene flow in .github/scripts/verify-release-hygiene.mjs and its tests/unit/release-hygiene.test.ts expectations around validating README doc link targets for prerelease vs stable branches (next-only vs release-branched logic).
• mohanagy/madar#463: Both PRs update the release-hygiene README link validation logic (from "next-only" prerelease checks to release-branch-aware checks) and adjust the corresponding unit test expectations for blob/next vs blob/main.
• mohanagy/madar#461: Both PRs change the release-hygiene verification logic and unit tests around GitHub README/documentation links needing to point to the correct branch (main vs next) based on the package version.

Poem

A rabbit hops with joy today,
The prerelease has gone away!
From next to stable, the links all shine,
Version 0.27.7 is signed and fine. 🐰✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately and concisely summarizes the main change: preparing a 0.27.7 stable release by promoting from a prerelease version.
Description check	✅ Passed	The description covers all required sections: summary of changes (three bullet points), comprehensive verification steps, and addresses testing checklist items comprehensively.
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.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ 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 release-0.27.7

---

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