ninepm 0.85.0 → 0.87.0

package/README.md

@@ -272,6 +272,20 @@ prints the `9pm domains list` command: once the domain is no longer listed, it h
 from 9pm. Such a domain shows as `removing` in `list` and `status` (`"removing": true` in `--json`),
 and `wait` on it exits `20`. Since 0.80.0.
 
+Since 0.86.0, a removal that finished (from `remove` or `9pm delete`) also says that after removal,
+visitors may see a TLS or routing error while the domain's DNS still points at 9pm. It names no
+record and adds no deletion advice of its own: what may be deleted is only the cleanup list printed
+above it, each record only if its value still matches. A removal still finishing gets no such line,
+since it is told to leave its records in place. A server that sends no cleanup list still gets it.
+
+Since 0.87.0, that line is followed by the order the staging rehearsal (#2182) demonstrated for a
+move to another host: point DNS at the new host, wait for the DNS TTL to pass, then remove the domain
+from 9pm. While caches update, some visitors may still reach 9pm or briefly see an error from the new
+host, and once DNS points away 9pm may show the domain as failed, which is expected. It links the
+custom-domain guide's "Moving a domain off 9pm" section on the site beside the control plane it
+talked to (staging's guide for `--api-url https://api-staging.9pm.ai`). A move to your own Cloudflare
+DNS zone was not rehearsed, so no order is printed for it; the guide says to contact support first.
+
 Since 0.84.0, `9pm domains removed [--owner <organisation>]` lists the DNS records you may delete
 after a removal that finished in the background: a `remove` that answered `releasing`, or a domain of
 a deleted app, finished later by the platform. It is the same list `remove` prints when it finishes

package/dist/index.d.ts

@@ -123,7 +123,7 @@ export interface DeletedSiteResult {
     metadata: boolean;
     errors?: string[];
 }
-export declare function deletedDomainLines(deleted: Pick<DeletedSiteResult, "customDomainCleanup" | "customDomainsReleasing">, options?: DomainFormatOptions): string[];
+export declare function deletedDomainLines(deleted: Pick<DeletedSiteResult, "customDomainCleanup" | "customDomainsReleasing" | "customDomainNames">, options?: DomainFormatOptions): string[];
 export interface CreatedRuntimeToken {
     token: string;
     appAccessToken: AppAccessToken;
@@ -133,7 +133,7 @@ export interface CreatedServiceToken {
     clientSecret: string;
 }
 export type FetchLike = (input: string | URL | Request, init?: RequestInit) => Promise<Response>;
-export declare const CLI_VERSION = "0.85.0";
+export declare const CLI_VERSION = "0.87.0";
 type CredentialBackend = "macos-keychain" | "windows-dpapi" | "linux-secret-service" | "file-plaintext" | "none";
 export interface StoredCredentialEntry {
     token: string;
@@ -897,6 +897,8 @@ export declare function getDomainSetupCleanup(options: DomainCommandOptions & {
 }): Promise<unknown>;
 export declare function domainSetupCleanupLines(body: unknown, hostname: string): string[];
 export declare function setupCleanupLines(hostname: string, records: DomainCleanupRecord[]): string[];
+export declare function customDomainMoveOffGuideUrl(options?: DomainFormatOptions): string;
+export declare function domainRemovedConsequenceLines(hostnames: string[], options?: DomainFormatOptions): string[];
 export declare function domainRemovalPendingLines(hostname: string, app: string, options: DomainFormatOptions): string[];
 export declare const FINISHED_REMOVAL_PAGES_PER_COMMAND = 20;
 export declare function getFinishedDomainRemovals(options: ApiOptions & {

package/dist/index.js

@@ -73,13 +73,24 @@ export function deletedDomainLines(deleted, options = {}) {
         for (const hostname of releasing) {
             lines.push(`${hostname} has stopped serving, but removing it upstream is still finishing; it finishes on its own. ${releaseNoCleanupLine(options)}`);
         }
+        // The consequence is said for the domains whose removal finished; one still releasing is
+        // told to leave its records alone, which repointing them would contradict.
+        const finished = [];
+        const names = Array.isArray(deleted.customDomainNames) ? deleted.customDomainNames : [];
+        for (const hostname of [...names, ...cleanups.map((cleanup) => cleanup?.hostname)]) {
+            if (typeof hostname !== "string" || hostname === "" || releasing.includes(hostname) || finished.includes(hostname))
+                continue;
+            finished.push(hostname);
+        }
+        if (finished.length > 0)
+            lines.push(...domainRemovedConsequenceLines(finished, options));
     }
     catch {
         return lines;
     }
     return lines;
 }
-export const CLI_VERSION = "0.85.0";
+export const CLI_VERSION = "0.87.0";
 const PUBLIC_DASHBOARD_URL = "https://9pm.ai/dashboard";
 const TOKEN_SERVICE = "9pm";
 const TOKEN_ACCOUNT = "default";
@@ -3875,6 +3886,25 @@ export function setupCleanupLines(hostname, records) {
         "If one of these names now holds a different value, that record is not ours: leave it. Keep the record that points the domain at 9pm.",
     ];
 }
+// The public guide's section on moving a domain off 9pm, on the site beside the control plane
+// this command talked to, so a staging run links staging's copy of the guide.
+export function customDomainMoveOffGuideUrl(options = {}) {
+    const dashboard = options.target ? dashboardUrlForApiUrl(options.target.apiUrl) : PUBLIC_DASHBOARD_URL;
+    return `${dashboard.replace(/\/dashboard$/, "")}/docs/custom-domains#move-off`;
+}
+// Said once a removal has finished (#2089): 9pm no longer holds the hostname, so while DNS
+// still points here a visitor reaches nothing that can answer for it. Which error they see is
+// not ours to promise. It names no record: what may be deleted is only the cleanup list above
+// it, which carries its own value condition, so this adds no deletion advice of its own. The
+// order is the one the staging rehearsal demonstrated for a move to another host (#2182,
+// scenario 2). A move to the owner's own Cloudflare zone was not rehearsed, so it gets no order.
+export function domainRemovedConsequenceLines(hostnames, options = {}) {
+    const subject = hostnames.length === 1 ? hostnames[0] : hostnames.join(", ");
+    return [
+        `After removal, visitors may see a TLS or routing error while DNS for ${subject} still points at 9pm.`,
+        `Moving a domain to another host? Point its DNS at the new host, wait for the DNS TTL to pass, then remove the domain from 9pm. While caches update, some visitors may still reach 9pm, or briefly see an error from the new host until it is set up for the name. Once DNS points away, 9pm may show the domain as failed; that is expected, so remove it. Guide: ${customDomainMoveOffGuideUrl(options)}`,
+    ];
+}
 // The command that lists what a removal finished in the background frees (#2068), aimed at the
 // same account and control plane as the command that printed it. Never a token.
 function domainsRemovedCommand(options, hostname) {
@@ -4466,6 +4496,8 @@ async function runDomainsCommand(command) {
         for (const line of domainCleanupLines(removal.cleanup))
             console.log(line);
     }
+    for (const line of domainRemovedConsequenceLines([removal.hostname], format))
+        console.log(line);
 }
 async function runDomainMove(action, base, format) {
     const hostname = normalizeDomainArg(action.hostname);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ninepm",
-  "version": "0.85.0",
+  "version": "0.87.0",
   "description": "CLI for deploying built apps to 9pm.ai.",
   "homepage": "https://9pm.ai",
   "keywords": [