@datadog/create-apps 0.2.0 → 0.2.2

package/README.md

@@ -66,10 +66,10 @@ Validate the bundled templates and exit. Intended for CI / development of this C
 
 ## Monorepos
 
-Use the development release to create an npm workspace and its first Datadog App:
+Use the latest release to create an npm workspace and its first Datadog App:
 
 ```bash
-npm create @datadog/apps@dev -- my-workspace --monorepo \
+npm create @datadog/apps@latest -- my-workspace --monorepo \
   --app-directory first-app --name "First App" --site datadoghq.com
 ```
 
@@ -78,7 +78,7 @@ The workspace keeps apps under `apps/*`, shared packages under `packages/*`, sha
 When the command detects an existing generated workspace, it adds the requested app to that workspace instead of creating a nested repository:
 
 ```bash
-npm create @datadog/apps@dev -- another-app --name "Another App"
+npm create @datadog/apps@latest -- another-app --name "Another App"
 ```
 
 Each app declares its own site. Interactive app creation prompts for it when `--site` is omitted; non-interactive creation uses `datadoghq.com` unless `--site` is passed.
@@ -86,7 +86,7 @@ Each app declares its own site. Interactive app creation prompts for it when `--
 Create a shared package from inside the workspace with:
 
 ```bash
-npm create @datadog/apps@dev -- --package shared-utils
+npm create @datadog/apps@latest -- --package shared-utils
 ```
 
 ### `--monorepo`
@@ -113,7 +113,7 @@ For a new monorepo, create a private GitHub repository with `gh`, set it as `ori
 
 Set or update `DATADOG_API_KEY` and `DATADOG_APP_KEY` on an existing workspace repository. The repository is read from `--github-repo` or the current `origin` remote.
 
-New monorepos include `.github/workflows/validate-datadog-apps.yml` for unconditional pull-request checks and `.github/workflows/deploy-datadog-apps.yml` for path-filtered default-branch uploads. Both execute `.github/scripts/validate-workspace.mjs` for React dependency alignment. The deployment workflow detects affected apps and runs the root-installed `datadog-apps upload` command from each selected app directory, with each app's own site and the Git commit as its version name, without requiring an app-owned `upload` script. The repository variable `DD_SITE` overrides every app's site when set.
+New monorepos include `.github/workflows/validate-datadog-apps.yml` for unconditional pull-request checks and `.github/workflows/deploy-datadog-apps.yml` for path-filtered default-branch uploads. Both execute `.github/scripts/validate-workspace.mjs` for React dependency alignment. The deployment workflow detects affected apps, installs the workspace once from the root lockfile, and runs [`DataDog/apps-github-action`](https://github.com/DataDog/apps-github-action) for each selected app directory with the root-installed CLI, each app's own site, and the Git commit as its version name, without requiring an app-owned `upload` script. The repository variable `DD_SITE` overrides every app's site when set.
 
 ## What Gets Created
 
@@ -121,7 +121,7 @@ The CLI will:
 
 - Create a new directory for your app
 - Generate all necessary files from the selected template, including:
-    - `datadog-app.config.json` — app definition and configuration (`datadogSite`, `id`, `name`)
+    - `datadog-app.config.json` — app definition and configuration (`datadogSite`, `id`, `name`, `tags`)
     - `vite.config.ts` — imports `datadog-app.config.json` and maps the flat fields into the `datadogVitePlugin(...)` call, layering env-dependent values on top
     - `package.json` (using the slugified directory name), source files, docs, and agent instructions
 - Integrate Datadog features like ErrorTracking, Metrics, and more... thanks to our [build-plugins](https://github.com/DataDog/build-plugins).