docs: record v11/1.2.2 as release candidate and correct the review-lock claim - #26
Conversation
…ck claim Two corrections, both verified against the live Google console and the Apps Script project on 2026-07-31. 1. Version 11 supersedes version 10. PR #22 (custom-function credential fix) merged 2026-07-29 22:01 UTC -- after version 10 was cut -- and changed Code.gs and Sidebar.html. Immutable version 11 was cut the same minute (18:01 EDT, the same instant in local time) and carries runtime 1.2.2; its Code.gs reads ADDON_VERSION = '1.2.2'. The Marketplace draft is still pinned to version 9, which was cut 2026-07-28 and predates BOTH #19 (OAuth verification prep) and #22. Version 11 is the release candidate and the docs now say so in every forward-looking place. 2. App Configuration is NOT locked during review. DEPLOYMENT_GUIDE.md and OAUTH_VERIFICATION.md both asserted the Marketplace App Configuration locks while Google reviews the draft. DOM inspection of the Cloud console disproves it: every input reports disabled:false, readOnly:false, no aria-disabled, and the Version field is a free-text input currently holding 9. Only the Store Listing tab locks ("The draft is in review and can't be edited"). That wrong assumption nearly drove an unnecessary cancel-and-recut of a submission that only ever needed a version repin. Nothing has been published; there is no live listing. test/public-claims.test.js is updated to pin 1.2.2/v11 and now also guards both corrections, so neither can silently regress. Verified: npm run validate passes -- 54 tests, deployment package, marketplace assets, portfolio, and secret scan all green. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 44 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe release documentation and public-claim tests now identify runtime 1.2.2 and immutable Apps Script version 11 as the Marketplace release candidate, with explicit version repinning and review-state guidance. ChangesRelease candidate update
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@OAUTH_VERIFICATION.md`:
- Around line 20-24: Update the status heading in OAUTH_VERIFICATION.md to July
31, 2026 so it matches the verification date recorded in the version 11
release-candidate block.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: f055a3e0-0d01-430a-a517-2a8a89ff162a
📒 Files selected for processing (4)
DEPLOYMENT_GUIDE.mdMARKETPLACE_LISTING.mdOAUTH_VERIFICATION.mdtest/public-claims.test.js
…y 29 evidence Addresses CodeRabbit review on #26: the heading claimed 'Status as of July 29' while the Current Google state block recorded July 31 console verification. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Two corrections to the release-state docs, both verified 2026-07-31 against the live Google console and the Apps Script project. Relates to #20.
1. Version 11 supersedes version 10
The docs treated v10 / runtime 1.2.1 as the reviewed release. It isn't the latest.
PR #22 (custom-function credential fix) merged at 2026-07-29T22:01:01Z, after v10 was cut, and changed
Code.gsandSidebar.html. Version 11 was cut at 18:01 EDT — the same instant (EDT is UTC−4), immediately after that merge. Confirmed independently by reading v11'sCode.gsin Project History:ADDON_VERSION = '1.2.2'.Why it matters: #22 fixes live custom functions returning
#AUTH_REQUIREDafter the sidebar successfully saves and tests an API key — the add-on's core path. The draft in review is pinned to v9, which predates both that fix and the OAuth verification prep in #19.2. App Configuration is not locked during review
DEPLOYMENT_GUIDE.mdandOAUTH_VERIFICATION.mdboth stated the App Configuration locks while Google reviews the draft, and that v10 should be entered "when Google makes App Configuration editable."DOM inspection of the Cloud console disproves it:
disabled: false,readOnly: false, noaria-disabled<input type="text">, currently holding9This mattered. The wrong assumption nearly drove a cancel-review-and-recut of a submission that only ever needed a version repin. The accurate rule is now recorded: Store Listing locks during review; App Configuration does not.
Guards
test/public-claims.test.jsalready pinned the docs to1.2.1/v10— that guard did its job and failed loudly on this change. It's updated to1.2.2/v11and extended so neither correction can silently regress:Verification
Scope
Docs and the claims test only — no runtime files touched, so v11 remains the valid immutable release. Nothing has been published; there is no live listing. The console repin (9 → 11) is a separate operator action tracked in #20.
🤖 Generated with Claude Code
Summary by CodeRabbit
Documentation
Tests