chore: version packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@devicesdk/cli@0.8.0

Minor Changes

• 47a0a95: Add a stateless Streamable-HTTP MCP server bundled into @devicesdk/server at /mcp - 15 tools covering projects, devices, env vars, script versions, commands, and offline docs search, authenticated via OAuth 2.1 (PKCE + dynamic client registration) or existing API tokens. Every tool re-enters the REST API in-process so behavior always matches the server's own version.

  This replaces the standalone @devicesdk/mcp npm package, which is removed - devicesdk init now scaffolds .mcp.json pointing at the server's own /mcp endpoint instead of npx @devicesdk/mcp. The docs site's MCP page is rewritten to match.

  GET /v1/projects/:projectId/devices/:deviceId/logs is un-deprecated: it was a permanent 410 in the Cloudflare era to protect a Durable Object rows-read quota that no longer exists on the self-hosted SQLite server, so it now returns a real cursor-paginated page of persisted logs. This is what makes devicesdk_device_logs a working MCP tool instead of a stub. The watcher WebSocket (/watch?backfillLimit=N) remains the dashboard's live-tailing path and is unchanged.

@devicesdk/server@0.3.0

Minor Changes

• 47a0a95: Add a stateless Streamable-HTTP MCP server bundled into @devicesdk/server at /mcp - 15 tools covering projects, devices, env vars, script versions, commands, and offline docs search, authenticated via OAuth 2.1 (PKCE + dynamic client registration) or existing API tokens. Every tool re-enters the REST API in-process so behavior always matches the server's own version.

  This replaces the standalone @devicesdk/mcp npm package, which is removed - devicesdk init now scaffolds .mcp.json pointing at the server's own /mcp endpoint instead of npx @devicesdk/mcp. The docs site's MCP page is rewritten to match.

  GET /v1/projects/:projectId/devices/:deviceId/logs is un-deprecated: it was a permanent 410 in the Cloudflare era to protect a Durable Object rows-read quota that no longer exists on the self-hosted SQLite server, so it now returns a real cursor-paginated page of persisted logs. This is what makes devicesdk_device_logs a working MCP tool instead of a stub. The watcher WebSocket (/watch?backfillLimit=N) remains the dashboard's live-tailing path and is unchanged.

@devicesdk/dashboard@0.4.2

Patch Changes

• 321ef7e: Fix account page crash when user object is missing usage/limits after login. The auth store now fetches the full user profile after login/register so usage and limits fields are always populated.

@devicesdk/website@0.1.8

Patch Changes

• 47a0a95: Add a stateless Streamable-HTTP MCP server bundled into @devicesdk/server at /mcp - 15 tools covering projects, devices, env vars, script versions, commands, and offline docs search, authenticated via OAuth 2.1 (PKCE + dynamic client registration) or existing API tokens. Every tool re-enters the REST API in-process so behavior always matches the server's own version.

  This replaces the standalone @devicesdk/mcp npm package, which is removed - devicesdk init now scaffolds .mcp.json pointing at the server's own /mcp endpoint instead of npx @devicesdk/mcp. The docs site's MCP page is rewritten to match.

  GET /v1/projects/:projectId/devices/:deviceId/logs is un-deprecated: it was a permanent 410 in the Cloudflare era to protect a Durable Object rows-read quota that no longer exists on the self-hosted SQLite server, so it now returns a real cursor-paginated page of persisted logs. This is what makes devicesdk_device_logs a working MCP tool instead of a stub. The watcher WebSocket (/watch?backfillLimit=N) remains the dashboard's live-tailing path and is unchanged.