@tailglow/cli 0.8.1 → 0.9.4

package/README.md

@@ -10,7 +10,9 @@ tglow login
 tglow projects list
 ```
 
-Node 22 or newer. `bun add -g` and `pnpm add -g` work the same way.
+Node 22 or newer. `bun add -g` and `pnpm add -g` work the same way. Update with
+`npm install -g @tailglow/cli@latest`. When a newer version is out, `tglow` says so in one line on
+stderr; it asks npm at most once a day.
 
 Prefer a shorter name? Alias it rather than installing over one:
 
@@ -151,7 +153,7 @@ Scan and validate locally without credentials:
 ```bash
 tglow import scan export.xml
 tglow import scan export.xml --record-path /HealthData/Record --full
-tglow import validate events.jsonl --timestamp-field /event/created_at
+tglow import validate events.jsonl
 ```
 
 Content detection supports XML, JSONL, JSON, CSV and TSV; use `--format` to resolve ambiguity.
@@ -194,11 +196,8 @@ graceful Ctrl-C. A cleanup failure is reported separately as `cleanup_error` and
 not change delivery status or acknowledged counts. Changes to the original after copying do not change the uploaded bytes. A failed
 full check sends no rows; successful checking cannot prevent a later delivery failure.
 
-`--timestamp-field` accepts a JSON pointer or an exact top-level field name. Source fields remain
-unchanged; the selected value sets request-level `ts`. Missing, invalid or timezone-ambiguous
-values fail validation. Selected dates must be between 1970-01-01 UTC and the current time, since earlier or future ingest timestamps cannot be preserved by the server. No timestamp field is selected automatically. Batches split whenever
-the exact parsed timestamp changes, which can produce one request per row, and otherwise stay
-within 500 rows and 1 MiB.
+Records keep their own fields, including their dates; Tailglow records when each batch arrived.
+Batches stay within 500 rows and 1 MiB.
 
 Only HTTP 202 acknowledges a batch. Upload stops on rejection or uncertain delivery and never
 retries automatically. The report includes `accepted_count` and the affected batch's inclusive

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tailglow/cli",
-  "version": "0.8.1",
+  "version": "0.9.4",
   "type": "module",
   "description": "The Tailglow command line. Every command is generated from the Tailglow API reference, so the CLI and the documentation can never describe different APIs.",
   "bin": {
@@ -35,6 +35,6 @@
     "@clack/prompts": "^1.2.0"
   },
   "devDependencies": {
-    "@types/bun": "^1.3.6"
+    "@types/bun": "^1.4.3"
   }
 }

package/src/commands.generated.js

@@ -7432,10 +7432,10 @@ export const CLI_COMMANDS = [
     "notes": [
       "Teams cannot be created with an API key. Use a signed-in user session.",
       "`name` defaults to `Team` and `billing_email` defaults to the authenticated user's email address when they are omitted.",
+      "`billing_email` cannot use the `@tailglow.io` domain.",
       "The team starts on the `pro_v1` plan with a generated logo. `billing_plan`, `status`, `logo_url`, `is_mfa_required`, `billing_address`, and `max_servers_per_project` are ignored on create. Send them to the update endpoint instead.",
       "There is a maximum number of teams a single user can create.",
       "The authenticated user is added to the new team as its Owner.",
-      "`billing_email` cannot use the `@tailglow.io` domain.",
       "`logo_url` must be a JPEG or PNG base64 data URI of at most 5 MB."
     ],
     "path_params": [],
@@ -7587,7 +7587,7 @@ export const CLI_COMMANDS = [
       "Teams cannot be updated with an API key. Use a signed-in user session.",
       "At least one field must be provided.",
       "Only team Owners can change billing, security, or account settings. Other members can update `name` and `logo_url` only.",
-      "`status`, `max_servers_per_project`, and `deleted_at` are managed by Tailglow and cannot be set by team members.",
+      "`status`, `max_servers_per_project`, and `deleted_at` are managed by Tailglow and cannot be set by team members, with one exception: an Owner restores a team scheduled for deletion by sending only `deleted_at` set to null.",
       "`status` requires `expected_status`, the status you loaded; the change is refused with a conflict if the team's status has changed since.",
       "Changing `is_mfa_required` requires a recently verified multi-factor sign-in.",
       "Moving to a plan that bills a payment method requires a valid payment method on the team.",
@@ -7761,7 +7761,7 @@ export const CLI_COMMANDS = [
         "name": "deleted_at",
         "type": "ISODateString | null",
         "required": false,
-        "description": "Date and time when the team is scheduled to be permanently deleted. Optional.",
+        "description": "Set to null, as the only field, to restore a team scheduled for deletion. Only Tailglow can set a date. Optional.",
         "allowed_values": [],
         "deprecated": null
       }
@@ -7781,7 +7781,8 @@ export const CLI_COMMANDS = [
       "Teams cannot be deleted with an API key. Use a signed-in user session.",
       "Only the team Owner can delete a team.",
       "The team must be active. Contact support to delete a suspended or blocked team.",
-      "Deletion is scheduled, not immediate. Permanent removal happens 40 days later, the team's projects and API keys are cancelled, and every signed-in member is signed out. An owner who signs back in before then cancels the deletion."
+      "Deletion is scheduled, not immediate. Permanent removal happens 40 days later. The team's API keys are deleted, its ingest keys are revoked, and its servers are scaled to zero.",
+      "Members lose access to the team at once but stay signed in to their other teams. Until permanent removal, an Owner can restore the team by updating it with `deleted_at` set to null."
     ],
     "path_params": [
       {
@@ -9254,6 +9255,9 @@ export const CLI_COMMANDS = [
     "notes": [
       "A server is a dedicated machine that receives and processes the project's data. Every project runs its own fleet.",
       "A server that is still coming up is returned with a status of `provisioning`, and a server on its way out with a status of `terminating`.",
+      "During a platform update, the server being replaced is returned with a status of `upgrading`. The `status` filter matches the status stored before the update, so it finds that server under `active`.",
+      "A platform update also adds a temporary server that takes each server's records while that server is replaced. It is not billed and is left out of this list; `is_deploy_surge=true` lists it instead.",
+      "`is_deploy_surge` accepts `true`, `false`, `1` or `0`.",
       "`after` and `before` are mutually exclusive."
     ],
     "path_params": [
@@ -9293,6 +9297,19 @@ export const CLI_COMMANDS = [
         ],
         "deprecated": null
       },
+      {
+        "name": "is_deploy_surge",
+        "type": "string",
+        "required": false,
+        "description": "Set true to list the temporary server a platform update adds instead of the project's own servers. Optional.",
+        "allowed_values": [
+          "true",
+          "false",
+          "1",
+          "0"
+        ],
+        "deprecated": null
+      },
       {
         "name": "limit",
         "type": "number",

package/src/config.js

@@ -17,7 +17,14 @@ export const CLI_CONFIGS = {
   DIRECTORY_MODE: 0o700,
   LOCK_RETRY_MS: 50,
   // The lock covers one small read and write, so waiting this long means its holder stopped.
-  LOCK_TIMEOUT_MS: 10_000
+  LOCK_TIMEOUT_MS: 10_000,
+  UPDATE_CHECK_URL: "https://registry.npmjs.org/@tailglow/cli/latest",
+  UPDATE_CHECK_PATH: join(homedir(), ".tailglow", "update-check.json"),
+  UPDATE_CHECK_INTERVAL_MS: 24 * 60 * 60 * 1_000,
+  // The check runs alongside the command, so this only delays a command that finishes sooner.
+  UPDATE_CHECK_TIMEOUT_MS: 1_500,
+  // Caps the stored check and npm's answer, which is about 2 KB.
+  UPDATE_CHECK_MAX_BYTES: 65_536
 };
 
 export const LOGIN_CONFIGS = {