Skip to content

chore(web): upgrade Next.js to 16.4.6 - #324

Open
khaliqgant wants to merge 1 commit into
mainfrom
chore/next-security-upgrade
Open

khaliqgant wants to merge 1 commit into
mainfrom
chore/next-security-upgrade

Conversation

@khaliqgant

@khaliqgant khaliqgant commented Nov 19, 2026 •

Copy link
Copy Markdown
Member

Summary

  • upgrade the exact Next.js dependency from 16.4.3 to the patched 16.4.6 release selected by the Next security upgrade agent
  • update only the matching package-lock entries for Next, @next/env, and platform SWC packages
  • preserve the existing experimental.agentUpgrade security setting in web/next.config.mjs
  • reassess the pinned OpenNext 1.20.1 compatibility patches and move their fail-closed Next version guard to 16.4.6

Verification

  • npm ci
  • npm exec --workspace web -- next --version → Next.js v16.4.6
  • npm run lint → pass with four pre-existing warnings
  • npm run typecheck → pass
  • npm test → 56 web files / 637 tests and 12 router files / 319 tests pass
  • npm run build → pass; the previous 16.4.3 security advisory stop/reminder no longer appears
  • node web/scripts/prepare-opennext.mjs → pass; both guarded adapter patch targets verified
  • OpenNext Cloudflare build → pass and worker bundle generated; existing dependency-copy warnings remain non-fatal

Notes

npm audit still reports 26 unrelated transitive advisories: 9 low, 7 moderate, 9 high, and 1 critical. This focused patch does not run npm audit fix or change unrelated dependencies.

No deploy or release is included.

@coderabbitai

coderabbitai Bot commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 25 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: c6e66473-1715-4293-a2ad-9f91ea777334
Commits

Reviewing files that changed from the base of the PR and between f79f267 and 58e5337.

Files ignored due to path filters: 1

  • package-lock.json is excluded by !**/package-lock.json
Files selected for processing: 2

  • web/package.json
  • web/scripts/prepare-opennext.mjs
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.

Share

Move to the patched release selected by the Next security upgrade agent. Update the exact dependency and matching lockfile entries while preserving the existing security upgrade configuration.
@khaliqgant
khaliqgant force-pushed the chore/next-security-upgrade branch from 8f8102b to 58e5337 Compare November 19, 2026 12:35
@github-actions

Copy link
Copy Markdown
Contributor

Preview deployed!

Environment URL
Web https://d871d38d-agentrelay-web.agent-workforce.workers.dev

This is a Cloudflare Workers preview version of this PR's build.

@khaliqgant
khaliqgant marked this pull request as ready for review November 19, 2026 12:44
@composalagent

composalagent Bot commented Nov 19, 2026 •

Copy link
Copy Markdown

Composal Verify · PR #324

Blocked Blocked · commit 58e53377124b

No preview within 1h; deploy and rerun

Diff assessment: Upgrades the web app’s Next.js runtime/build dependency from 16.4.3 to 16.4.6, updates matching lockfile packages, and adjusts the OpenNext compatibility version guard.

Relevant scenarios (not run)

Result Scenario Persona Outcomes Duration
Blocked Blocked A visitor can locate documentation resources in the homepage footer — — —
Blocked Blocked A visitor can skip homepage navigation using the keyboard — — —
Blocked Blocked A visitor can select the real-time team coordination feature — — —
Blocked Blocked A visitor can select the homepage timezone coordination feature — — —
Blocked Blocked A visitor can select public-agent debugging using the keyboard — — —
Blocked Blocked A visitor can open Relay documentation from the homepage footer — — —
Blocked Blocked A visitor can return home after using skip navigation — — —
Blocked Blocked A visitor can open Relayfile documentation from the homepage footer — — —
Blocked Blocked A visitor can revisit Relayfile documentation using browser history — — —
Blocked Blocked A visitor can resume Relayhistory after visiting the homepage — — —
Blocked Blocked A visitor can open Flows from the public homepage footer — — —
Blocked Blocked A visitor can select the Flows code-review example by keyboard — — —
Blocked Blocked A visitor can open Flows documentation from its product page — — —
Blocked Blocked A visitor can inspect wordmark choices in the Brand Kit — — —
Blocked Blocked A visitor can open the web theme using keyboard activation — — —
Blocked Blocked A visitor can navigate past disabled Brand button specimens — — —
Blocked Blocked A visitor can identify the focused Brand specimen button — — —
Blocked Blocked A visitor can read the reusable web theme token snippet — — —
Blocked Blocked A visitor can open Relay documentation from the Pear page — — —
Blocked Blocked A visitor can open the agent gallery from Pear — — —
Blocked Blocked A visitor can browse use cases from the agent gallery — — —
Blocked Blocked A visitor can locate the pull-request automation use case — — —
Blocked Blocked A visitor can read the PR Reviewer configuration requirements — — —
Blocked Blocked A visitor can read the Repo Hygiene configuration requirements — — —
Blocked Blocked A visitor can return to use cases after reading hygiene details — — —
Blocked Blocked A visitor can read the Linear Implementer configuration requirements — — —
Blocked Blocked A visitor can read the Granola Prospect configuration requirements — — —
Blocked Blocked A visitor can read the news-monitor configuration requirements — — —
Blocked Blocked A visitor can read the Vendor Monitor configuration requirements — — —
Blocked Blocked A visitor can read the music-alert configuration requirements — — —
Blocked Blocked A visitor can read the multi-agent team coordination description — — —
Blocked Blocked A visitor can read the infrastructure-monitor configuration requirements — — —
Blocked Blocked A visitor can read the Inbox Buddy configuration requirements — — —
Blocked Blocked A visitor can read the Linear Slack configuration requirements — — —
Blocked Blocked A visitor can reveal the public agent-authoring prompt — — —
Blocked Blocked A visitor can open technical docs from messaging marketing — — —
Blocked Blocked A visitor can find support guidance through the homepage footer — — —
Blocked Blocked A visitor can read the privacy policy from support — — —
Blocked Blocked A visitor can focus the privacy policy telemetry reference — — —
Blocked Blocked A visitor can open trust guidance through keyboard navigation — — —
Blocked Blocked A reader can reach public documentation from the homepage footer — — —
Blocked Blocked A reader can find the available agent connection options — — —
Blocked Blocked A reader can open workspace onboarding from connection guidance — — —
Blocked Blocked A developer can identify the workspace credential required for onboarding — — —
Blocked Blocked A developer can find harness installation guidance before spawning agents — — —
Blocked Blocked A developer can locate guidance for reconnecting an existing workspace — — —
Blocked Blocked A developer can find workspace key safety guidance while onboarding — — —
Blocked Blocked A developer can learn the documented restrictions on observer tokens — — —
Blocked Blocked A developer can find expiration requirements for temporary access tokens — — —
Blocked Blocked A developer can discover the available workspace diagnostic interfaces — — —
Blocked Blocked A developer can distinguish channel and direct message destinations — — —
Blocked Blocked A developer can find token-specific channel membership guidance — — —
Blocked Blocked A developer can find handle-array examples for private group messages — — —
Blocked Blocked A developer can find reply and reaction guidance for DMs — — —
Blocked Blocked A developer can find pagination guidance for retrieving message threads — — —
Blocked Blocked A developer can find reaction aggregation and removal guidance — — —
Blocked Blocked A developer can find parent identifiers in threaded sending examples — — —
Blocked Blocked A developer can find the required client for action registration — — —
Blocked Blocked A developer can find typed predicates for asynchronous action outcomes — — —
Blocked Blocked A developer can trace orchestration guidance to failure recovery — — —
Blocked Blocked A developer can find replay-safe event handler contract guidance — — —
Blocked Blocked A developer can find the supported event listener selector styles — — —
Blocked Blocked A developer can locate the canonical asynchronous action lifecycle — — —
Blocked Blocked A reader can find account-free Relay Connect guest prerequisites — — —
Blocked Blocked A reader can reach native Connect setup recovery guidance — — —
Blocked Blocked A reader can find Relay Connect room error recovery guidance — — —
Blocked Blocked A reader can trace fleet onboarding to connection verification guidance — — —
Blocked Blocked A reader can find macOS fleet recovery through page contents — — —
Blocked Blocked A reader can find fleet management follow-up documentation — — —
Blocked Blocked A reader can find the separate public-agent registration prerequisites — — —
Blocked Blocked A reader can trace public-agent activation to ownership verification guidance — — —
Blocked Blocked A reader can find serverless public-agent deployment verification guidance — — —
Blocked Blocked A reader can find public-agent runtime and status guidance — — —
Blocked Blocked A developer can find consistent existing-identity registration guidance — — —
Blocked Blocked A reader can switch archived Channels guidance to the latest version — — —
Blocked Blocked A reader can switch current Channels guidance to an archived version — — —
Blocked Blocked A reader can return to anchored archived Channels guidance — — —
Blocked Blocked A reader can return to anchored current Getting started guidance — — —
Blocked Blocked A reader can return to directly opened archived Channels guidance — — —
Blocked Blocked A reader can select appropriate Python onboarding in latest Quickstart — — —
Blocked Blocked A visitor can begin Google sign-in from the login page — — —
Blocked Blocked A visitor can open agent signup from the Teams page — — —
Blocked Blocked A visitor can find Google sign-in on the login page — — —
Blocked Blocked A visitor can read the reviewer sign-in page — — —
Blocked Blocked A visitor can see both signup options on the Teams page — — —
Blocked Blocked A visitor gets not found at the retired Flows onboarding URL — — —
Blocked Blocked A visitor is asked to sign in for desktop setup — — —
Blocked Blocked A visitor is asked to sign in to approve a device — — —
Blocked Blocked A visitor is sent to Google from Flows 'Try Free' — — —
Blocked Blocked A visitor is sent to Google from Teams sign up — — —
Blocked Blocked A visitor sees a device code prefilled from the link — — —
Blocked Blocked A visitor sees an expired session message on login — — —
Blocked Blocked A visitor sees 'Invite not found' for a bad invite link — — —
Blocked Blocked A visitor sees the invite notice on login — — —
Blocked Blocked A visitor sees the reviewer wrong-password message — — —
Blocked Blocked A reader can reach every current docs page from the sidebar — — —
Blocked Blocked A visitor can find a desktop build and checksum for every supported platform — — —
Blocked Blocked A visitor can reach Solo, Team and Talk setup from the homepage — — —
Run a scenario again

Relevant to this diff

  • A developer can discover the available workspace diagnostic interfaces · Run
  • A developer can distinguish channel and direct message destinations · Run
  • A developer can find consistent existing-identity registration guidance · Run
  • A developer can find expiration requirements for temporary access tokens · Run
  • A developer can find handle-array examples for private group messages · Run
  • A developer can find harness installation guidance before spawning agents · Run
  • A developer can find pagination guidance for retrieving message threads · Run
  • A developer can find parent identifiers in threaded sending examples · Run
  • A developer can find reaction aggregation and removal guidance · Run
  • A developer can find replay-safe event handler contract guidance · Run
  • A developer can find reply and reaction guidance for DMs · Run
  • A developer can find the required client for action registration · Run
  • A developer can find the supported event listener selector styles · Run
  • A developer can find token-specific channel membership guidance · Run
  • A developer can find typed predicates for asynchronous action outcomes · Run
  • A developer can find workspace key safety guidance while onboarding · Run
  • A developer can identify the workspace credential required for onboarding · Run
  • A developer can learn the documented restrictions on observer tokens · Run
  • A developer can locate guidance for reconnecting an existing workspace · Run
  • A developer can locate the canonical asynchronous action lifecycle · Run
  • A developer can trace orchestration guidance to failure recovery · Run
  • A reader can find account-free Relay Connect guest prerequisites · Run
  • A reader can find fleet management follow-up documentation · Run
  • A reader can find macOS fleet recovery through page contents · Run
  • A reader can find public-agent runtime and status guidance · Run
  • A reader can find Relay Connect room error recovery guidance · Run
  • A reader can find serverless public-agent deployment verification guidance · Run
  • A reader can find the available agent connection options · Run
  • A reader can find the separate public-agent registration prerequisites · Run
  • A reader can open workspace onboarding from connection guidance · Run
  • A reader can reach every current docs page from the sidebar · Run
  • A reader can reach native Connect setup recovery guidance · Run
  • A reader can reach public documentation from the homepage footer · Run
  • A reader can return to anchored archived Channels guidance · Run
  • A reader can return to anchored current Getting started guidance · Run
  • A reader can return to directly opened archived Channels guidance · Run
  • A reader can select appropriate Python onboarding in latest Quickstart · Run
  • A reader can switch archived Channels guidance to the latest version · Run
  • A reader can switch current Channels guidance to an archived version · Run
  • A reader can trace fleet onboarding to connection verification guidance · Run

137 more scenarios in Composal.

Why these 98 scenarios were selected
  • A visitor can locate documentation resources in the homepage footer: Next upgrade affects page rendering; opening home and checking footer resources covers rendered output.
  • A visitor can skip homepage navigation using the keyboard: Next upgrade affects rendered pages and hydration; skip-link keyboard steps cover preserved focus behavior.
  • A visitor can select the real-time team coordination feature: Next upgrade affects client hydration; clicking the real-time feature checks its interactive selection.
  • A visitor can select the homepage timezone coordination feature: Next upgrade affects client hydration; clicking Flatten timezones checks interactive selection.
  • A visitor can select public-agent debugging using the keyboard: Next upgrade affects client hydration; keyboard feature selection checks preserved interaction.
  • A visitor can open Relay documentation from the homepage footer: Next upgrade affects routing and rendering; footer Docs activation checks destination heading and command.
  • A visitor can return home after using skip navigation: Next upgrade affects navigation runtime; returning from docs with Back checks homepage restoration.
  • A visitor can open Relayfile documentation from the homepage footer: Next upgrade affects routing and rendering; footer RelayFile Docs activation checks its destination article.
  • A visitor can revisit Relayfile documentation using browser history: Next upgrade affects navigation runtime; Back and Forward check Relayfile article restoration.
  • A visitor can resume Relayhistory after visiting the homepage: Next upgrade affects routing and history; returning from home checks the Relayhistory article is restored.
  • A visitor can open Flows from the public homepage footer: Next upgrade affects routing and rendering; homepage Flows link checks the product destination heading.
  • A visitor can select the Flows code-review example by keyboard: Next upgrade affects client hydration; keyboard activation checks the Flows code-review example changes.
  • A visitor can open Flows documentation from its product page: Next upgrade affects routing and rendering; Explore the docs checks the Flows article loads.
  • A visitor can inspect wordmark choices in the Brand Kit: Next upgrade affects page rendering; opening Brand and inspecting its gallery checks rendered asset content.
  • A visitor can open the web theme using keyboard activation: Next upgrade affects navigation and rendering; keyboard theme-link activation checks the destination content.
  • A visitor can navigate past disabled Brand button specimens: Next upgrade affects rendered controls; clicking and tabbing checks disabled specimens remain outside the focus path.
  • A visitor can identify the focused Brand specimen button: Next upgrade affects rendered controls; tabbing after Search example checks the focused button's accessible name.
  • A visitor can read the reusable web theme token snippet: Next upgrade affects page rendering; loading the theme page and checking its token snippet covers rendered content.
  • A visitor can open Relay documentation from the Pear page: Next upgrade affects routing and rendering; Pear's docs link checks the Getting started article and command.
  • A visitor can open the agent gallery from Pear: Next upgrade affects routing and rendering; Pear's Agents link checks the gallery destination heading.
  • A visitor can browse use cases from the agent gallery: Next upgrade affects routing and rendering; Browse use cases checks the use-case destination heading.
  • A visitor can locate the pull-request automation use case: Next upgrade affects page rendering and navigation; selecting the PR use case checks its section content.
  • A visitor can read the PR Reviewer configuration requirements: Next upgrade affects route loading; opening PR Reviewer checks its Configure content renders.
  • A visitor can read the Repo Hygiene configuration requirements: Next upgrade affects route loading; opening Repo Hygiene checks its Configure content renders.
  • A visitor can return to use cases after reading hygiene details: Next upgrade affects navigation history; Back from Repo Hygiene checks the use-case section is restored.
  • A visitor can read the Linear Implementer configuration requirements: Next upgrade affects route loading; opening Linear Implementer checks its Configure content renders.
  • A visitor can read the Granola Prospect configuration requirements: Next upgrade affects route loading; opening Granola Prospect checks its Configure content renders.
  • A visitor can read the news-monitor configuration requirements: Next upgrade affects route loading; opening Hacker News Monitor checks its Configure content renders.
  • A visitor can read the Vendor Monitor configuration requirements: Next upgrade affects route loading; opening Vendor Monitor checks its Configure content renders.
  • A visitor can read the music-alert configuration requirements: Next upgrade affects route loading; opening Spotify Releases checks its Configure content renders.
  • A visitor can read the multi-agent team coordination description: Next upgrade affects page rendering; loading use cases checks the multi-agent coordination section renders.
  • A visitor can read the infrastructure-monitor configuration requirements: Next upgrade affects route loading; opening Cloudflare Monitor checks its Configure content renders.
  • A visitor can read the Inbox Buddy configuration requirements: Next upgrade affects route loading; opening Inbox Buddy checks its Configure content renders.
  • A visitor can read the Linear Slack configuration requirements: Next upgrade affects route loading; opening Linear Slack checks its Configure content renders.
  • A visitor can reveal the public agent-authoring prompt: Next upgrade affects client hydration; Show prompt checks that the agent-authoring disclosure expands.
  • A visitor can open technical docs from messaging marketing: Next upgrade affects routing and rendering; messaging's docs link checks the destination article and command.
  • A visitor can find support guidance through the homepage footer: Next upgrade affects routing and rendering; footer Support navigation checks the support page loads.
  • A visitor can read the privacy policy from support: Next upgrade affects routing and rendering; support's Privacy Policy link checks its destination heading.
  • A visitor can focus the privacy policy telemetry reference: Next upgrade affects page rendering and navigation; privacy keyboard steps check the inline link's focus path.
  • A visitor can open trust guidance through keyboard navigation: Next upgrade affects routing and rendering; keyboard trust-link activation checks the Security and trust page.
  • A reader can reach public documentation from the homepage footer: Next upgrade affects routing and rendering; footer Docs navigation checks the Getting started article and command.
  • A reader can find the available agent connection options: Next upgrade affects docs rendering and navigation; contents selection checks Ways To Connect content.
  • A reader can open workspace onboarding from connection guidance: Next upgrade affects route loading; the Build a workspace link checks Quickstart renders its Install section.
  • A developer can identify the workspace credential required for onboarding: Next upgrade affects docs rendering; selecting Create a workspace checks credential guidance remains available.
  • A developer can find harness installation guidance before spawning agents: Next upgrade affects docs rendering and navigation; selecting the spawn section checks its installation command.
  • A developer can locate guidance for reconnecting an existing workspace: Next upgrade affects docs routing; navigating to Workspaces and its join section checks reconnect guidance.
  • A developer can find workspace key safety guidance while onboarding: Next upgrade affects docs routing and rendering; navigating to Authentication checks workspace-key safety guidance.
  • A developer can learn the documented restrictions on observer tokens: Next upgrade affects docs rendering; selecting Observer Tokens checks the documented restrictions remain visible.
  • A developer can find expiration requirements for temporary access tokens: Next upgrade affects docs rendering and navigation; Lifecycle selection checks token expiration guidance.
  • A developer can discover the available workspace diagnostic interfaces: Next upgrade affects docs rendering and navigation; Diagnostics selection checks CLI and MCP links render.
  • A developer can distinguish channel and direct message destinations: Next upgrade affects docs rendering and navigation; scenario opens Messaging and checks Core Send Paths.
  • A developer can find token-specific channel membership guidance: Next upgrade affects docs rendering; scenario loads Channels and navigates to membership guidance.
  • A developer can find handle-array examples for private group messages: Next upgrade affects docs rendering and hydration; scenario opens DMs and selects Group DMs.
  • A developer can find reply and reaction guidance for DMs: Next upgrade affects docs rendering and navigation; scenario traverses DM sections and checks messageId examples.
  • A developer can find pagination guidance for retrieving message threads: Next upgrade affects docs rendering; scenario opens Threads and checks the selected pagination section.
  • A developer can find reaction aggregation and removal guidance: Next upgrade affects docs rendering; scenario loads reaction guidance and selects its list/removal section.
  • A developer can find parent identifiers in threaded sending examples: Next upgrade affects docs rendering; scenario loads sending guidance and navigates to threaded replies.
  • A developer can find the required client for action registration: Next upgrade affects client routing; scenario navigates from Introduction to Actions and checks registration guidance.
  • A developer can find typed predicates for asynchronous action outcomes: Next upgrade affects docs rendering and hydration; scenario selects completion guidance and checks predicates.
  • A developer can trace orchestration guidance to failure recovery: Next upgrade affects docs navigation; scenario traverses orchestration sections and checks failure guidance.
  • A developer can find replay-safe event handler contract guidance: Next upgrade affects docs rendering; scenario loads Event handlers and checks the selected handler contract.
  • A developer can find the supported event listener selector styles: Next upgrade affects client routing and hydration; scenario changes docs pages and navigates handler sections.
  • A developer can locate the canonical asynchronous action lifecycle: Next upgrade affects client routing; scenario navigates from Event handlers to Events and checks action lifecycle.
  • A reader can find account-free Relay Connect guest prerequisites: Next upgrade affects docs rendering; scenario loads Relay Connect and selects guest prerequisites.
  • A reader can reach native Connect setup recovery guidance: Next upgrade affects page routing; scenario follows the native setup guide and checks recovery content.
  • A reader can find Relay Connect room error recovery guidance: Next upgrade affects docs rendering; scenario loads Relay Connect and checks its troubleshooting section.
  • A reader can trace fleet onboarding to connection verification guidance: Next upgrade affects page navigation; scenario follows Fleet setup and traverses connection verification guidance.
  • A reader can find macOS fleet recovery through page contents: Next upgrade affects docs rendering and hydration; scenario uses page contents to reach macOS recovery guidance.
  • A reader can find fleet management follow-up documentation: Next upgrade affects docs navigation; scenario traverses fleet sections and checks Next steps links.
  • A reader can find the separate public-agent registration prerequisites: Next upgrade affects client routing; scenario navigates from Introduction to public-agent registration guidance.
  • A reader can trace public-agent activation to ownership verification guidance: Next upgrade affects docs rendering and navigation; scenario traverses activation and ownership sections.
  • A reader can find serverless public-agent deployment verification guidance: Next upgrade affects docs rendering; scenario selects delivery-type and serverless sections of public-agent docs.
  • A reader can find public-agent runtime and status guidance: Next upgrade affects docs rendering and navigation; scenario selects harness and state sections.
  • A developer can find consistent existing-identity registration guidance: Next upgrade affects route rendering; scenario opens SDK and public-agent routes and checks registration content.
  • A reader can switch archived Channels guidance to the latest version: Next upgrade affects client routing; scenario switches archived docs to latest and checks the destination article.
  • A reader can switch current Channels guidance to an archived version: Next upgrade affects client routing; scenario switches current Channels to archived docs and checks content.
  • A reader can return to anchored archived Channels guidance: Next upgrade affects router history; scenario switches docs versions then returns to anchored archived guidance.
  • A reader can return to anchored current Getting started guidance: Next upgrade affects router history and fragments; scenario checks Back restores Getting started#solo and its version.
  • A reader can return to directly opened archived Channels guidance: Next upgrade affects router history; scenario checks Back restores directly opened archived Channels.
  • A reader can select appropriate Python onboarding in latest Quickstart: Next upgrade affects rendering and hydration; scenario changes docs language, reloads, and checks Python mode.
  • A visitor can begin Google sign-in from the login page: Next upgrade affects runtime routing; scenario exercises login's Google sign-in redirect.
  • A visitor can open agent signup from the Teams page: Next upgrade affects client routing; scenario follows Teams signup to /signup/teams and checks its heading.
  • A visitor can find Google sign-in on the login page: Next upgrade affects route rendering; scenario checks login renders its sign-in button and new-user link.
  • A visitor can read the reviewer sign-in page: Next upgrade affects route rendering; scenario checks reviewer login renders its heading and submit button.
  • A visitor can see both signup options on the Teams page: Next upgrade affects route rendering; scenario checks Teams renders its heading and both signup links.
  • A visitor gets not found at the retired Flows onboarding URL: Next upgrade affects route resolution; scenario checks the retired onboarding URL still renders not found.
  • A visitor is asked to sign in for desktop setup: Next upgrade affects runtime routing; scenario checks anonymous desktop onboarding redirects to Google sign-in.
  • A visitor is asked to sign in to approve a device: Next upgrade affects rendering and hydration; scenario submits a device code and checks the sign-in-required state.
  • A visitor is sent to Google from Flows 'Try Free': Next upgrade affects runtime routing; scenario follows Flows Try Free through to Google sign-in.
  • A visitor is sent to Google from Teams sign up: Next upgrade affects runtime routing; scenario follows Teams signup through to Google sign-in.
  • A visitor sees a device code prefilled from the link: Next upgrade affects query-driven rendering; scenario checks user_code prefills the device authorization field.
  • A visitor sees an expired session message on login: Next upgrade affects query-driven rendering; scenario checks authError=state displays the expired-session message.
  • A visitor sees 'Invite not found' for a bad invite link: Next upgrade affects dynamic route handling; scenario loads an invalid invite and checks its error state.
  • A visitor sees the invite notice on login: Next upgrade affects query-driven rendering; scenario checks invite_token displays the workspace invitation notice.
  • A visitor sees the reviewer wrong-password message: Next upgrade affects query-driven rendering; scenario checks reviewer error=invalid renders the password error.
  • A reader can reach every current docs page from the sidebar: Next upgrade affects docs routing and rendering; scenario traverses sidebar routes and verifies destination articles.
  • A visitor can find a desktop build and checksum for every supported platform: Next upgrade affects rendering and hydration; scenario opens All downloads and checks platform builds and checksums.
  • A visitor can reach Solo, Team and Talk setup from the homepage: Next upgrade affects client routing; scenario follows homepage Get started and checks destination setup sections.
Recent verification history
Commit Result Started
58e53377124b Blocked Blocked 2026-11-19 12:44 UTC

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 19, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-19T12:46:10.896249Z 58e5337 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Devin Review

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant