@mitralab.io/platform-sdk 1.1.0-beta.0 → 1.1.0-beta.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -2,6 +2,14 @@
2
2
 
3
3
  All notable changes to this project are documented in this file.
4
4
 
5
+ ## 1.1.0-beta.2
6
+
7
+ `1.1.0-beta.1` was published from `main` before this change landed, so it still depends on Core `0.2.0-beta.0`; use `1.1.0-beta.2`.
8
+
9
+ - Depend on `@mitralab.io/sdk-core@0.2.0-beta.1`, which reads back integration configs with a
10
+ null `templateId` (configs born from an inline definition). The browser adapter still only
11
+ lists and executes integration configs; authoring stays in the studio SDK and the MCP.
12
+
5
13
  ## 1.1.0-beta.0
6
14
 
7
15
  - Complete native Function sync, async, polling, cancellation, and anonymous public execution.
package/README.md CHANGED
@@ -250,7 +250,7 @@ List the current app's saved configs without exposing the Core admin module:
250
250
  const configs = await mitra.integration.list({ page: 0, size: 20, sort: "alias,asc" })
251
251
  ```
252
252
 
253
- The Integration producer derives the app from the authenticated token, so this list is app-scoped.
253
+ The Integration producer derives the app from the authenticated token, so this list is app-scoped. A listed config carries `templateId: null` when it was created from an inline definition instead of a catalog template.
254
254
 
255
255
  Execute a predefined resource:
256
256
 
@@ -335,7 +335,7 @@ npm install
335
335
  npm run check
336
336
  ```
337
337
 
338
- Platform `1.1.0-beta.0` targets exactly `@mitralab.io/sdk-core@0.2.0-beta.0`. Until that Core prerelease is published, local validation uses its matching tarball through `MITRA_SDK_CORE_TARBALL`. The manifest and lock keep the registry spec and the tarball's verified integrity; root `npm ci` becomes available after Core is published. Do not commit a `file:` dependency.
338
+ Platform `1.1.0-beta.2` targets exactly `@mitralab.io/sdk-core@0.2.0-beta.1`, published on the `beta` dist-tag. The manifest and lock keep the registry spec and its verified integrity, so `npm ci` resolves Core from a clean checkout. To validate against a Core prerelease that is not published yet, point `MITRA_SDK_CORE_TARBALL` at its tarball for the package smoke test. Do not commit a `file:` dependency.
339
339
 
340
340
  The build produces ESM, CommonJS, `.d.ts`, and `.d.cts` artifacts. Package checks inspect the public tarball with Are The Types Wrong, install it into an isolated consumer, and validate ESM, CommonJS, and TypeScript resolution.
341
341
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@mitralab.io/platform-sdk",
3
- "version": "1.1.0-beta.0",
3
+ "version": "1.1.0-beta.2",
4
4
  "description": "JavaScript/TypeScript SDK for building apps on the Mitra Platform",
5
5
  "type": "module",
6
6
  "sideEffects": false,
@@ -62,7 +62,7 @@
62
62
  "url": "https://github.com/mitralab-dev/mitra-platform-sdk/issues"
63
63
  },
64
64
  "dependencies": {
65
- "@mitralab.io/sdk-core": "0.2.0-beta.0",
65
+ "@mitralab.io/sdk-core": "0.2.0-beta.1",
66
66
  "mitra-interactions-sdk": "1.0.60-beta.48"
67
67
  },
68
68
  "devDependencies": {