Skip to content

The easy-to-use open source Business Intelligence and Embedded Analytics tool that lets everyone work with data :bar_chart:

chore(sdk): bump sdk version and use 64-alpha dist tag for data apps (#79011)

Phoomparin Mano6db26cc0df92
diff --git a/enterprise/frontend/src/embedding-sdk-package/package.template.json b/enterprise/frontend/src/embedding-sdk-package/package.template.json
index 39a93dac7ea..6827dfc4aa5 100644
--- a/enterprise/frontend/src/embedding-sdk-package/package.template.json
+++ b/enterprise/frontend/src/embedding-sdk-package/package.template.json
@@ -1,8 +1,8 @@
{
"name": "@metabase/embedding-sdk-react",
- "version": "0.64.0-alpha.0",
+ "version": "0.64.0-alpha.1",
"sdkRelease": {
- "distTag": "alpha",
+ "distTag": "64-alpha",
"tagAsLatest": false
},
"description": "Metabase Embedding SDK for React",
diff --git a/skills/metabase-data-app-setup/SKILL.md b/skills/metabase-data-app-setup/SKILL.md
index 4bf3cdd8331..ef884766f7b 100644
--- a/skills/metabase-data-app-setup/SKILL.md
+++ b/skills/metabase-data-app-setup/SKILL.md
@@ -78,10 +78,10 @@ Once the template is in `<repo>/data_apps/<slug>/` (run everything below from th
2. Pin `@metabase/embedding-sdk-react` to the published data-apps tag (the template ships with `*`):
```bash
- npm install @metabase/embedding-sdk-react@63-data-apps
+ npm install @metabase/embedding-sdk-react@64-alpha
```
- This resolves to the current internal-testing SDK build with the `@metabase/embedding-sdk-react/data-app` entrypoint (the app's APIs) and the `@metabase/embedding-sdk-react/data-app-dev/config` entrypoint `vite.config.ts` uses (the dev/build preset, which serves the sandbox entry). Do not use `latest`, `63-stable`, or a generic `^0.63.x` range for data apps until the data-app SDK surface is promoted out of the internal tag.
+ This resolves to the current internal-testing SDK build with the `@metabase/embedding-sdk-react/data-app` entrypoint (the app's APIs) and the `@metabase/embedding-sdk-react/data-app-dev/config` entrypoint `vite.config.ts` uses (the dev/build preset, which serves the sandbox entry). Do not use `latest` or `64-stable` as data apps are not yet released.
3. **Ensure the repo-root `.gitignore` ignores `.env.local`** — do this *before* creating any credentials file so the secret can never be committed. Create the `.gitignore` if the repo doesn't have one, then add the entry if it's missing:
```bash