zuplo 7.12.7 → 7.13.2

package/docs/articles/api-key-best-practices.mdx

@@ -4,13 +4,6 @@ sidebar_label: Best Practices
 applies_to:
   product: gateway
   hosting: all
-  differs:
-    managed-dedicated: >-
-      Validation results are cached in the regions of your dedicated instance
-      instead of across 300+ edge locations.
-    self-hosted: >-
-      Validation results are cached by your gateways inside your own cluster,
-      and Zuplo cloud services provide key storage and management.
 ---
 
 A well-designed API key system handles much more than authentication. It covers

package/docs/articles/api-key-management.mdx

@@ -4,13 +4,6 @@ sidebar_label: Overview
 applies_to:
   product: gateway
   hosting: all
-  differs:
-    managed-dedicated: >-
-      Keys are validated and cached in the regions of your dedicated instance
-      instead of across 300+ edge locations.
-    self-hosted: >-
-      Your gateways validate keys inside your own cluster, and Zuplo cloud
-      services provide key storage and management.
 ---
 
 Zuplo provides a fully managed API key authentication system that you can add to

package/docs/articles/custom-domains.mdx

@@ -100,13 +100,22 @@ verification. Please be patient if this happens.
 By default, you can also use the url on `zuploapp.com` although, if you prefer
 that to be removed contact support and we can disable it for you.
 
-:::caution
+:::note
+
+If you use Cloudflare as your DNS provider, you can set the `CNAME` record to
+either proxy status:
 
-If you use Cloudflare as your DNS provider, you MUST enable Cloudflare Proxy on
-your custom domain.
+- **DNS only**: Traffic goes straight to Zuplo.
+- **Proxied**: Traffic passes through your own Cloudflare zone first, so your
+  zone's settings, such as WAF rules and caching, apply before the request
+  reaches Zuplo.
 
 ![Cloudflare proxy status](../../public/media/custom-domains/a40beef2-9eed-44fd-a41e-3f337afbaee2.png)
 
+If you see Cloudflare Error 1014 (CNAME Cross-User Banned), check that the
+domain is added to your Zuplo project and that its status is active. See
+[Cloudflare Customers](#cloudflare-customers) for other limitations.
+
 :::
 
 ### 4. Redeploy

package/docs/articles/monetization/stripe-integration.md

@@ -176,13 +176,23 @@ Stripe dashboard.
 
 When a customer clicks "Subscribe" in your Developer Portal:
 
-1. A Stripe Checkout Session is created so the customer can enter a payment
+1. The customer is redirected to Stripe Checkout, where they enter and save a
+   payment method
+2. The customer returns to the Developer Portal and confirms the subscription
+3. The subscription is created, and an API key is generated scoped to the plan's
+   entitlements
+4. Stripe issues an invoice for the subscription and charges the saved payment
    method
-2. The customer is redirected to Stripe Checkout to enter payment details
-3. On successful payment, the subscription is created
-4. An API key is generated scoped to the subscription's plan entitlements
-5. The customer is redirected back to the Developer Portal, where they can
-   immediately see their subscription, usage dashboard, and API key
+5. The customer can immediately see their subscription, usage dashboard, and API
+   key in the Developer Portal
+
+:::note
+
+Stripe Checkout only collects a payment method, so the Checkout page doesn't
+show the plan name, price, or line items. Customers see the charge on the
+subscription's invoice.
+
+:::
 
 ### Plan changes (upgrades/downgrades)
 

package/docs/articles/source-control-setup-github.mdx

@@ -165,8 +165,29 @@ With GitHub connected, you get:
     settings and reconnect it.
   </FaqItem>
   <FaqItem question="What happens if I rename my repository?">
-    Renaming your repository will break the connection. You must disconnect and
-    reconnect to restore the link.
+    Nothing changes for your project. Zuplo updates the connection to the new
+    repository name automatically, and pushes keep deploying as before.
+  </FaqItem>
+  <FaqItem question="What happens if I transfer my repository to another GitHub organization?">
+
+    Zuplo doesn't follow a transfer. After you move the repository, pushes stop
+    deploying and no error appears. To move the repository without losing
+    deployments:
+
+    1. Install the [Zuplo GitHub app](https://github.com/apps/zuplo) on the new
+       organization and give it access to the repository.
+    2. Transfer the repository in GitHub.
+    3. Open your
+       [project settings](https://portal.zuplo.com/+/account/project/settings/general),
+       select **Source Control**, and click **Disconnect**.
+    4. Connect the project to the same repository in its new organization and
+       click **Link project**. If your production branch isn't `main`, set it
+       again under **Default Branch**.
+    5. Push a commit to confirm that deployments run again.
+
+    Your existing deployments, environment URLs, and custom domains keep serving
+    traffic throughout the move.
+
   </FaqItem>
   <FaqItem question="Can I connect multiple Zuplo projects to the same repo?">
     No, each Zuplo project must be connected to a unique GitHub repository.

package/docs/articles/troubleshooting-deployments-and-git-sync.mdx

@@ -138,7 +138,8 @@ mean the connection is no longer authorized:
 
 - The OAuth authorization Zuplo uses to reach the provider has **expired or been
   revoked**.
-- The repository was **renamed or moved**, which breaks the existing connection.
+- The repository was **moved** to another organization, which breaks the
+  existing connection.
 - The Git app was **uninstalled** or lost access to the repository in the
   provider's settings.
 
@@ -161,9 +162,10 @@ After reconnecting, retrieving branches should succeed again.
 
 :::caution
 
-Renaming a repository breaks the Zuplo connection. If you renamed or moved the
-repository, disconnect and reconnect to restore the link. See
-[Rename or Move Project](./rename-or-move-project.mdx) for details.
+Zuplo follows a GitHub repository rename automatically. Moving a repository to
+another organization breaks the connection, and pushes stop deploying. To
+restore it, follow
+[the steps for transferring a repository](./source-control-setup-github.mdx#frequently-asked-questions).
 
 :::
 

package/docs/concepts/api-keys.md

@@ -3,15 +3,6 @@ title: API Keys
 applies_to:
   product: gateway
   hosting: all
-  differs:
-    managed-dedicated: >-
-      Gateway services that run with your dedicated instance validate API keys,
-      instead of the 300+ edge locations. See [Managed Dedicated
-      architecture](../dedicated/architecture.mdx).
-    self-hosted: >-
-      Zuplo cloud services provide API key management, and your self-hosted
-      gateway validates keys against them. See
-      [Self-Hosted](../self-hosted/overview.md).
 ---
 
 Zuplo includes a fully managed API key system with global edge validation,

package/docs/dedicated/architecture.mdx

@@ -20,10 +20,11 @@ A managed dedicated instance of Zuplo consists of the following components:
   receives incoming requests, routes them to the appropriate backend, and
   returns the response to the client. The gateway handles authentication,
   authorization, rate limiting, and other features.
-- **Gateway Services**: Zuplo, being a highly distributed gateway, uses services
-  to facilitate features such as
+- **Gateway Services**: Zuplo-hosted services that power features such as
   [Rate Limiting](../getting-started/gateway/add-rate-limiting/index.mdx) and
-  [API Key Authentication](../articles/api-key-management.mdx).
+  [API Key Authentication](../articles/api-key-management.mdx). Every Zuplo
+  deployment, including managed dedicated instances, uses the same gateway
+  services.
 - **Control Plane**: The Control Plane manages the configuration of the Zuplo
   Gateway. It deploys new configurations, manages the lifecycle of the Zuplo
   Gateway, and monitors its health.
@@ -92,9 +93,6 @@ instance of Zuplo and how the components interact with each other.
     <DiagramNode id="gateway" variant="zuplo">
       Zuplo Gateway
     </DiagramNode>
-    <DiagramNode id="services" variant="zuplo">
-      Gateway Services
-    </DiagramNode>
   </DiagramGroup>
   <DiagramGroup id="customer-vpc" label="Customer Private Network">
     <DiagramNode id="backend">Backend</DiagramNode>
@@ -102,6 +100,9 @@ instance of Zuplo and how the components interact with each other.
   <DiagramNode id="control" variant="zuplo">
     Control Plane
   </DiagramNode>
+  <DiagramNode id="services" variant="zuplo">
+    Gateway Services
+  </DiagramNode>
   <DiagramEdge from="client" to="gateway" />
   <DiagramEdge from="gateway" to="backend" />
   <DiagramEdge from="gateway" to="services" fromSide="bottom" toSide="top" />

package/docs/getting-started/gateway/deploy-to-the-edge/index.mdx

@@ -227,8 +227,8 @@ when running commits, pulls or try to open a pull request.
   collaborator. This can be verified by going to the GitHub repository >
   Settings > Collaborators section. You'll need admin permissions to the
   repository.
-- If the GitHub repository has been renamed or moved to a different
-  organization, try disconnecting and reconnecting to it. You can do this by
-  going to your Zuplo project's settings > Source Control section
+- If the GitHub repository has been moved to a different organization,
+  disconnect and reconnect to it in your Zuplo project's settings > Source
+  Control section. Zuplo follows a repository rename automatically.
 
 <TutorialPager build="gateway" method="portal" step="deploy-to-the-edge" />

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "zuplo",
-  "version": "7.12.7",
+  "version": "7.13.2",
   "type": "module",
   "description": "The official Zuplo CLI for local development and platform management",
   "homepage": "https://zuplo.com/docs/cli/overview",
@@ -32,9 +32,9 @@
     "zuplo": "zuplo.js"
   },
   "dependencies": {
-    "@zuplo/cli": "7.12.7",
-    "@zuplo/core": "7.12.7",
-    "@zuplo/runtime": "7.12.7",
-    "@zuplo/test": "7.12.7"
+    "@zuplo/cli": "7.13.2",
+    "@zuplo/core": "7.13.2",
+    "@zuplo/runtime": "7.13.2",
+    "@zuplo/test": "7.13.2"
   }
 }