@turbobase/cli 1.1.11 → 1.1.12

package/LICENSE

@@ -1,4 +1,4 @@
-TurboBase CLI — Software Licence
+Turbobase CLI — Software Licence
 
 Copyright (c) 2025-2026 Adam Kundrat. All rights reserved.
 
@@ -10,10 +10,10 @@ handed to customers on a public registry: a customer who installs it needs the
 right to run it, and "no rights granted" would not give them that.
 
 1. GRANT. Subject to your compliance with these terms and to an active
-   agreement with the copyright holder covering the TurboBase service, you are
+   agreement with the copyright holder covering the Turbobase service, you are
    granted a non-exclusive, non-transferable, non-sublicensable, revocable
    licence to install and run this software, for the sole purpose of
-   authoring, testing, and deploying extensions to TurboBase instances you are
+   authoring, testing, and deploying extensions to Turbobase instances you are
    authorised to access. Installing it on your own machines and on continuous
    integration runners you control is permitted under this grant.
 
@@ -27,7 +27,7 @@ right to run it, and "no rights granted" would not give them that.
 
 3. RESERVATION. All rights not expressly granted here are reserved by the
    copyright holder. This licence covers this software only. It grants no
-   rights in the TurboBase service, which is governed by your service
+   rights in the Turbobase service, which is governed by your service
    agreement, and no rights in any trademark.
 
 4. THIRD-PARTY COMPONENTS. This software incorporates third-party open source
@@ -44,5 +44,5 @@ right to run it, and "no rights granted" would not give them that.
    THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
 7. TERMINATION. This licence terminates automatically if you breach any of
-   these terms, and when your agreement covering the TurboBase service ends.
+   these terms, and when your agreement covering the Turbobase service ends.
    On termination you must stop using this software and delete all copies.

package/README.md

@@ -1,6 +1,6 @@
 # turbobase
 
-The command-line interface to your [TurboBase](https://turbobase.io/) instance.
+The command-line interface to your [Turbobase](https://turbobase.io/) instance.
 
 Build and ship the apps your team uses, author the extensions that run inside
 your instance, promote a reviewed configuration from sandbox to production, and
@@ -9,7 +9,7 @@ model — all from one binary, over your instance's HTTP API.
 
 **Full documentation: [docs.turbobase.io](https://docs.turbobase.io/)**
 
-TurboBase is a managed service: your instance is provisioned and operated for
+Turbobase is a managed service: your instance is provisioned and operated for
 you at [console.turbobase.io](https://console.turbobase.io/). This CLI drives an
 instance you already have — it is not a way to run the platform yourself.
 
@@ -42,7 +42,7 @@ Requires **Node 22, or 24 and newer**.
 
 ## Sign in
 
-Mint a personal access token in your TurboBase app under **Settings › Access
+Mint a personal access token in your Turbobase app under **Settings › Access
 tokens**, then hand it to the CLI. This is the only sign-in path.
 
 ```sh
@@ -75,7 +75,7 @@ go deeper.
 | Group | What it does |
 | --- | --- |
 | `auth` | Sign in, switch the active instance, manage stored credentials. |
-| `apps` | Build, preview, and ship hosted apps served inside your TurboBase app. |
+| `apps` | Build, preview, and ship hosted apps served inside your Turbobase app. |
 | `ext` | Author, test, deploy, and observe extensions — hooks and conduits — plus the marketplace. |
 | `project` | Scaffold a project and generate the files an AI agent session reads. |
 | `release` | Ship your project from your own CI — deploy, status, rollback, list. |
@@ -86,7 +86,7 @@ go deeper.
 ## Ship a hosted app
 
 Hosted apps are served from your instance at `/a/<slug>`, so anyone who can open
-your TurboBase app can open them — no separate hosting, no separate login.
+your Turbobase app can open them — no separate hosting, no separate login.
 
 Because the app is served same-origin, it inherits your instance's auth: no
 sign-in page to build, no callback, no CORS, no app-owned keys. Visitors who
@@ -103,7 +103,7 @@ turbobase apps list
 
 `create` is required before the first deploy — or pass `deploy --create` to fold
 it in. `init` is local-only and touches nothing on the instance. The build runs
-**on your machine**; TurboBase serves the result.
+**on your machine**; Turbobase serves the result.
 
 `push` and `deploy` are deliberately separate: `push` records the source on the
 instance so the app can be pulled and refined from another machine (or by a
@@ -125,7 +125,7 @@ can still be promoted. Set the app's display name and description in
 `turbobase.json` — the manifest is applied on every deploy. The slug is fixed
 once created: it is the URL, and nothing redirects the old one.
 
-→ [Build apps on TurboBase](https://docs.turbobase.io/build-apps/)
+→ [Build apps on Turbobase](https://docs.turbobase.io/build-apps/)
 
 ## Author and deploy extensions
 
@@ -201,7 +201,7 @@ turbobase ext publish hooks/<file>.ts --name acme-recipes --pkg-version 1.0.0
 ```
 
 Both need a registry credential — set `TURBOBASE_REGISTRY_URL` and
-`TURBOBASE_REGISTRY_TOKEN` from the token TurboBase support issues you. It is
+`TURBOBASE_REGISTRY_TOKEN` from the token Turbobase support issues you. It is
 separate from your instance's access token and is revocable on its own.
 Publishing requires a publisher allowlist.
 
@@ -217,7 +217,7 @@ turbobase project ci     # writes .github/workflows/turbobase-release-deploy.yml
 ```
 
 It runs in **your** repo on **your** runner and uploads your checkout's bytes —
-TurboBase clones nothing and holds no GitHub App key. The CLI is the equal front
+Turbobase clones nothing and holds no GitHub App key. The CLI is the equal front
 door if you'd rather drive it yourself:
 
 ```sh
@@ -255,7 +255,7 @@ or `NO_COLOR=1`.
 
 ## Versioning
 
-This package's version is the TurboBase release it shipped with, so
+This package's version is the Turbobase release it shipped with, so
 `turbobase --version` tells you which platform release the CLI was built and
 tested against. A version reaches the `latest` tag only after that release is
 live in production.
@@ -264,11 +264,11 @@ live in production.
 
 ## Documentation
 
-- [Getting started](https://docs.turbobase.io/getting-started/what-is-turbobase/) — what TurboBase is, and the path to a live instance
+- [Getting started](https://docs.turbobase.io/getting-started/what-is-turbobase/) — what Turbobase is, and the path to a live instance
 - [CLI overview](https://docs.turbobase.io/cli/overview/) — installing, signing in, and the shape of the tool
 - [CLI reference](https://docs.turbobase.io/cli/reference/) — every command, its flags, and an example
-- [Build apps on TurboBase](https://docs.turbobase.io/build-apps/) — building against your instance
-- [Extending TurboBase](https://docs.turbobase.io/extending/writing-hooks/) — hooks, conduits, sandboxes, promotion
+- [Build apps on Turbobase](https://docs.turbobase.io/build-apps/) — building against your instance
+- [Extending Turbobase](https://docs.turbobase.io/extending/writing-hooks/) — hooks, conduits, sandboxes, promotion
 
 Questions the docs don't answer: [support@turbobase.io](mailto:support@turbobase.io).