This page is the mandatory upgrade entry point for CYPEX v2.0.0. It is written for operators who run CYPEX in production and need a single walkthrough that covers every breaking change in this release.

Audience. Read this end-to-end before opening the maintenance window. It links out to detailed pages for each topic; follow every link in the order presented.

v2.0.0 introduces seven platform-level changes. Each one is breaking or behavior-changing for at least one class of deployment.

This page is the operational counterpart to the conceptual pages in the Organizations section. It targets operators who run CYPEX, the PostgreSQL Application Platform, in production and need to perform the four day-to-day jobs: create, edit, and disable organizations; give users access to an organization; configure org-scoped application visibility (Schema Access); and troubleshoot misconfigurations.

For the why behind the model, see the conceptual pages linked below.

Read these four pages before walking through the procedures:

Operator-facing upgrade guides, one per major version. Start here before deploying a new major version of CYPEX in production.

• Upgrade to v2.0.0 — the mandatory upgrade entry point for v2.0.0: pre-upgrade checklist, breaking changes, RLS impact, SSO migration, Organizations migration, Connectors enablement, post-upgrade verification, and rollback constraints.

• Migrations — the technical reference and step-by-step migration walkthroughs that this guide links out to.
• Release Management — for per-application version control on top of an upgraded platform.

v2.0.0 replaces the single long-lived JWT with an access token / refresh token pair. This page explains the model, the settings that govern it, and the two configuration mistakes that break a deployment.

Under the old model a token was minted at login and stayed valid for its whole lifetime. Deactivating a user or changing their role did nothing until that token expired — potentially days later.