Release Method v2.1.0

[flyingrobots]

Summary

Prepare and cut Method v2.1.0 after the GitHub Issues tracker migration and sponsor-evidence template follow-up.

Scope

• Version bump to 2.1.0.
• Changelog entry.
• Internal release packet.
• User-facing release notes.
• Release verification witness.

Current blocker

Npm publication requires an authenticated npm session. npm whoami currently returns E401 on this machine.

Acceptance criteria

• Release prep branch validates locally.
• Release PR merges to main.
• v2.1.0 tag and GitHub Release are created after npm auth/package visibility decision.
• npm publication is verified or explicitly deferred with evidence.

[coderabbitai]

🔗 Related PRs

#3 - Add CI gates, close out cycle 0006, and refine guidance [merged]
#6 - Automated Witness Capture (Cycle 0020) [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[flyingrobots]

Release prep is merged to main via PR #68 / merge commit b353e85f3dd5ec872393f6c355dd307039c08fb8.

Validated before merge:

• npm run method -- doctor: pass, 0 errors / 0 warnings
• npm audit --omit=dev: pass, 0 vulnerabilities
• npm run lint: pass
• npm run build: pass
• npm test: pass, 23 files / 317 tests
• npm pack --dry-run: pass, flyingrobots-method-2.1.0.tgz
• GitHub CI on PR Prepare Method v2.1.0 release #68: pass

Remaining blocker before tag/publish: npm auth/package visibility. npm whoami returned E401 locally, unauthenticated npm view @flyingrobots/method version returned 404, and the public unscoped method@2.0.0 package belongs to a different maintainer/repo. Do not tag v2.1.0 until npm publication path is confirmed or explicitly deferred.

[flyingrobots]

Release tag and GitHub Release are created:

• Tag: v2.1.0
• GitHub Release: https://github.com/flyingrobots/method/releases/tag/v2.1.0

Npm publish is still blocked by npm 2FA. npm publish --access public reached the registry and failed with EOTP: one-time password required.

Next step: rerun publish with a current OTP, for example:

npm publish --access public --otp <code>

Then verify:

npm view @flyingrobots/method version

Do not close this issue until npm reports 2.1.0.

[flyingrobots]

Closing this release tracker by explicit maintainer decision.

GitHub Release is complete:

• https://github.com/flyingrobots/method/releases/tag/v2.1.0
• Tag v2.1.0 is pushed.
• Local/repo validation passed before release prep merged.

Npm publication is intentionally deferred. npm publish --access public reached the registry but failed with EOTP because npm requires a one-time password for publish. We are not blocking the GitHub release on npm publication for this release pass.

[flyingrobots]

GitHub Release v2.1.0 is published. Npm publication is explicitly deferred by maintainer decision due OTP requirement.