chore: release tokenleak 2.1.1#134
Conversation
|
Caution Review failedPull request was closed or merged during review No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (10)
📝 WalkthroughWalkthroughThis PR is a patch version bump from ChangesVersion Bump 2.1.0 → 2.1.1
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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. Comment |
Summary
2.1.1.bun.lockbafter the version bump.Release Validation
npm view tokenleak version dist-tags --jsonconfirmed npm latest is2.1.0.PATH="/Users/yansh/.bun/bin:$PATH" bun run checkPATH="/Users/yansh/.bun/bin:$PATH" bun test packages/core/src/index.test.ts packages/cli/src/cli.test.tsPATH="/Users/yansh/.bun/bin:/opt/homebrew/bin:$PATH" bun run prepublishbun dist/tokenleak --versionprintstokenleak 2.1.1.npm pack --dry-run --jsonfromdist/containsREADME.md,package.json, and executabletokenleak.npm publish --dry-runfromdist/succeeds fortokenleak@2.1.1.Publish Note
Actual npm publish is not completed yet because
npm whoamireturned E401 in this environment. Runnpm login/ refresh npm auth before publishing.Summary by CodeRabbit