Repository navigation
Release Method v2.1.0 #67
Description
Activity
🔗 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 plancommand 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!
Release prep is merged to
mainvia PR #68 / merge commitb353e85f3dd5ec872393f6c355dd307039c08fb8.Validated before merge:
npm run method -- doctor: pass, 0 errors / 0 warningsnpm audit --omit=dev: pass, 0 vulnerabilitiesnpm run lint: passnpm run build: passnpm test: pass, 23 files / 317 testsnpm 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 whoamireturned E401 locally, unauthenticatednpm view @flyingrobots/method versionreturned 404, and the public unscopedmethod@2.0.0package belongs to a different maintainer/repo. Do not tagv2.1.0until npm publication path is confirmed or explicitly deferred.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 publicreached the registry and failed withEOTP: 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.- Tag:
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.0is pushed. - Local/repo validation passed before release prep merged.
Npm publication is intentionally deferred.
npm publish --access publicreached the registry but failed withEOTPbecause npm requires a one-time password for publish. We are not blocking the GitHub release on npm publication for this release pass.GitHub Release v2.1.0 is published. Npm publication is explicitly deferred by maintainer decision due OTP requirement.
Summary
Prepare and cut Method v2.1.0 after the GitHub Issues tracker migration and sponsor-evidence template follow-up.
Scope
Current blocker
Npm publication requires an authenticated npm session.
npm whoamicurrently returns E401 on this machine.Acceptance criteria