Release

[evereq]

No description provided.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 917a343c-c48d-40a9-87ff-299b9cbdfed0

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch stage

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[codacy-production]

Not up to standards ⛔

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[greptile-apps]

Greptile Summary

Refreshes the documentation site’s design and release infrastructure.

• Adds comprehensive Support and Ever Teams Kit documentation.
• Redesigns navigation, sidebars, footer, typography, responsive tables, branding, and theme styling.
• Adds a support-page sidebar promotion and new image assets.
• Updates CodeQL and container-build workflow runners and action versions.

Confidence Score: 5/5

The PR appears safe to merge with no concrete changed-code failure identified.

The documentation routes, Docusaurus theme extension points, conditional search configuration, and sidebar customizations remain consistent with the repository’s current configuration and dependencies.

T-Rex Logs

What T-Rex did

• Created and attached a proof for the posted P1 finding.
• Validated the updated Support route by comparing pre-change and post-change states, confirming the new surface renders in both dark and light modes with the sidebar promo and a visible footer, and noting runtime contradictions where the Support route shows React errors while /advanced-guide/ does not.
• Collected and reviewed the artifacts (screenshots, videos, and logs) to inspect the UI changes and runtime behavior on the Support route.

_{Ran code and verified through T-Rex}

Important Files Changed

Filename	Overview
website/docusaurus.config.ts	Updates branding, navigation, search placement, fonts, footer links, and theme configuration without an identified actionable defect.
website/docs/advanced-guide/support.mdx	Replaces the placeholder support document with a structured support guide and reusable presentation components.
website/src/components/SidebarPromo/index.tsx	Adds a route-specific promotional panel for the desktop support-page sidebar.
website/src/theme/MDXComponents.tsx	Wraps Markdown tables in keyboard-focusable horizontal scrolling containers.
website/sidebars.ts	Adds Kit navigation and retains hidden Advanced Guide entries needed for document sidebar association.
.github/workflows/k8s-build.yml	Updates runner selection and Docker-related action major versions for the image publishing workflow.
.github/workflows/codeql.yml	Updates runner selection and the checkout action for CodeQL analysis.

Comments Outside Diff (1)

1. General comment

   Support MDX causes full-page React hydration failure

   • Bug
     • Opening the production /advanced-guide/support/ route produces 42 recoverable hydration errors (React error #418) followed by error #423, meaning React abandons the server-rendered tree and client-renders the root. The UI eventually appears, but users pay unnecessary rerendering cost and the browser console is flooded. The comparable /advanced-guide/ route produces zero errors.
   • Cause
     • The changed website/docs/advanced-guide/support.mdx places blank-line Markdown content inside literal JSX <p> elements at lines 121, 132, 321, and 369. Generated HTML demonstrates that these become empty styled paragraphs followed by separate unstyled paragraphs—for example <p class="heroLead_QYIT"></p><p>Ever Teams is developed…</p>—creating server/client markup disagreement across many elements.
   • Fix
     • Keep paragraph text directly inside each JSX <p> without separating blank lines, or replace these wrappers with MDX-safe components that accept children. Rebuild and verify that the production route reports zero onRecoverableError console events in both themes.

   _{Ran code and verified through T-Rex}

_{Reviews (1): Last reviewed commit: "Merge pull request #72 from ever-co/deve..." | Re-trigger Greptile}