Repository navigation
chore(release): 6.3.0 - #167
Conversation
|
Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits. |
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (3)
Cache: Disabled due to data retention organization setting Knowledge base: Disabled due to data retention organization setting 📝 WalkthroughWalkthroughVersion field bumped from 6.2.0 to 6.3.0 across three manifest files: the plugin manifest, release-please configuration, and package manifest. ChangesVersion Bump to 6.3.0
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Poem
✨ Finishing Touches🧪 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
Cuts 6.3.0 — a minor release covering the work merged on top of 6.2.0:
feat(privacy): mask account emails across all display surfaces (the minor-bump driver)fix: resolve 16 deep-audit findings (data-loss, rotation, redaction, concurrency)test: deep stress suite for the audited subsystemsVersion bump
All three version sources moved 6.2.0 → 6.3.0 in lockstep:
package.json.release-please-manifest.json.codex-plugin/plugin.json(enforced bytest/doc-parity.test.ts)Verification
npm run build: succeedsnpm run typecheck+npm run lint: cleannpm test: 96 files, 2487 passed, 1 skippednpm publish --dry-run: succeeds —oc-codex-multi-auth-6.3.0.tgz, 465 kB, 430 files, public accessNotes
.omc/RELEASE_RULE.mddocuments the derived release process (local cache).🤖 Generated with Claude Code
Summary by CodeRabbit
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 version bump 6.2.0 → 6.3.0 across all four version sources. no logic, dependency, or configuration changes are included — the substantive work (email masking, audit fixes, stress tests) landed in #164–#166 and this pr merely cuts the release.
package.jsonandpackage-lock.jsonversion fields updated in lockstep; no dependency tree mutations..codex-plugin/plugin.jsonand.release-please-manifest.jsonupdated to match, satisfying thedoc-paritytest gate.Confidence Score: 5/5
this pr touches only version strings — no logic, no token handling, no filesystem paths, no concurrency code.
all four files change exactly one string each (6.2.0 → 6.3.0). the lockfile shows no dependency-tree mutations, and the doc-parity test enforces that plugin.json stays in sync. nothing here can regress runtime behavior.
no files require special attention — every change is a mechanical version string update.
Important Files Changed
Flowchart
%%{init: {'theme': 'neutral'}}%% flowchart TD A[6.2.0 tag] -->|#164 feat: email masking| B[feature merged] B -->|#165 fix: 16 audit findings| C[fixes merged] C -->|#166 test: deep stress suite| D[tests merged] D -->|chore release #167| E[version bump 6.3.0] E --> F[package.json] E --> G[package-lock.json] E --> H[.codex-plugin/plugin.json] E --> I[.release-please-manifest.json] F & G & H & I --> J[doc-parity test passes] J --> K[npm publish --dry-run OK] K --> L[manual npm publish after merge + tag]Reviews (1): Last reviewed commit: "chore(release): bump version to 6.3.0" | Re-trigger Greptile