@cube-dev/platform-client 0.15.0 → 0.17.0

package/CHANGELOG.md

@@ -9,6 +9,28 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 <!-- Curate public-facing entries here before the next release. -->
 
+## [0.17.0] - 2026-10-04
+
+### Added
+
+- `notificationEnabled` on the create and update bodies and the response of `POST`/`PUT …/scheduled-tasks`: when `true`, the creator gets a notification in Cube's inbox when a run finishes, whether it succeeds or fails. Defaults to `false`.
+- `expectedVersion` on the report update body (`PUT …/reports/{reportId}`): when it does not match the stored version of the report, the update answers `409` instead of overwriting a newer save.
+- `GET /api/v1/deployments/{deploymentId}/agent-suggestions` returns the starter prompts an agent offers in chat, for the agents the caller can use (CUB-3700).
+- `GET /api/v1/deployments/{deploymentId}/reports/{reportId}/file` returns a report's definition as canonical JSON text (`content`) with its SHA-256 (`hash`), and `PATCH` on the same path changes part of it by exact-text replacement (CUB-5237).
+- `GET /api/v1/deployments/{deploymentId}/workbooks/{workbookId}/dashboard/file` returns the classic dashboard draft as canonical JSON text (`content`) with its SHA-256 (`hash`), and `PATCH` on the same path changes part of it by exact-text replacement (CUB-5237).
+- `POST /api/v1/deployments/{deploymentId}/environments/{environmentId}/tokens` and `POST …/tokens-for-meta-sync` now return `data.scopes`, the runtime scopes signed into the token (CUB-4728). A requested scope the caller may not hold is dropped rather than refused, so this is how a caller tells which ones it got — for example, whether a meta-sync token carries `meta-private`. The token listing (`GET …/tokens`) is unchanged. The `data` type of the `POST …/tokens` response is now the schema `CreatedDeploymentEnvironmentToken` (was `DeploymentEnvironmentToken`), so code that names the old type for that response needs updating.
+
+### Changed
+
+- `POST /api/v1/deployments/{deploymentId}/scheduled-tasks` now requires the new deployment-scoped `ScheduledTasksCreate` permission and answers `403` without it (CUB-4940). Every built-in role grants it, so only a custom role can withhold it. A custom role saved before this release keeps creating tasks on every deployment where it can use the agent, until an admin saves it without the permission; a custom role saved since holds it only where an admin grants it. Reading, updating, pausing, running and deleting a task are unchanged, including for a creator who no longer holds the permission. The RBAC action enums (`Policy.actions`, the resource user/group policy schemas and their inherited variants) gained `ScheduledTasksCreate`.
+- `POST /api/v1/deployments/{deploymentId}/environments/{environmentId}/tokens-for-meta-sync` can now sign the `meta-private` scope (CUB-4728). It still always signs `meta`, and adds `meta-private` when it is listed in `scopes` and the caller holds data model read access (`SchemaRead`) on the deployment, or is an admin on a tenant with RBAC off; otherwise it is dropped rather than signed, and any other requested scope is still ignored. A token carrying it may pass `include_private=true` to the Metadata API (`/v1/entities`, `/v1/entities/{name}`, `/v1/entities/all`) to read private cubes, views and members with their full definitions; data access policies still apply. `POST …/tokens` does not sign `meta-private`.
+
+## [0.16.0] - 2026-09-29
+
+### Changed
+
+- `POST /api/v1/deployments/{deploymentId}/workbooks/{workbookId}/publish` (`WorkbooksPublicController.publishDashboard`) publishes the saved dashboard draft when `config` is omitted, so the request only needs `workbookId`. An explicit `config` remains supported for existing clients.
+
 ## [0.15.0] - 2026-09-25
 
 ### Added