Repository navigation
chore(release): version packages - #177
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
November 10, 2026 00:00
4fe75c1 to
35466f5
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 10, 2026 00:22
35466f5 to
6f875a1
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish 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
@cloudhal/api@0.7.0
Minor Changes
mcp()andjwt()plugins run in the Studio's auth instance when the runtime has a stable public origin: the admin Worker uses its origin,cloudhal studioneeds--base-url/CLOUDHAL_BASE_URL(it logs why OAuth is off otherwise), andCLOUDHAL_MCP_OAUTH=offturns it off. Access tokens are Ed25519 JWTs bound to/mcpfor one hour, refresh tokens rotate with a 30-second reuse window, and each connection is approved on Studio's new consent screen (/oauth/consent), which narrows the requested scopes by the member's role and records anagent_grantsrow (migration0031_oauth). A token resolves to the same principal an agent key does; revoking a connection (DELETE /api/agent-grants/:id) or removing the member refuses it on its next call. The Better Auth family moves to 1.7.18. Client registration (CIMD, DCR) and the "Connected agents" screen follow in Phase 3.Patch Changes
d363160: Remote MCP clients can now register themselves (RFC-0044 Phase 3a, ADR-0045). Clients that name an HTTPS Client ID Metadata Document as their
client_id(Claude Code, Codex, VS Code) are accepted through@better-auth/cimd, fetched with the media import's SSRF-safe transport (pinned on Node, DoH-checked on Workers; https only, public addresses only, no redirects, 5 KB, 5 s). Clients without one (Cursor) use dynamic client registration at/api/auth/oauth2/register: public clients only, rate-limited per address and per day, capped at 5,000, and pruned by the scheduler after 30 unused days. Document clients are fetched at most hourly per client, with budgets in Cloudhal's own counters that never lock out stored clients, a cap of 5,000 that evicts unused clients (the well-known clients' hosts are exempt), pruning after three hours unused, and a failed refetch that refuses the client; migration0032_oauth_client_kind_indexindexes them. Redirect URIs must be https, loopback http (any port) or a native app's private-use scheme (cursor,vscode, reverse-domain,CLOUDHAL_MCP_REDIRECT_SCHEMES), and the client host list applies at every authorization. With DCR off, the clients it registered earlier cannot start new authorizations. The consent screen shows client names plain and short, a document client's host first, and marks self-registered clients as unverified.CLOUDHAL_MCP_CIMD=off,CLOUDHAL_MCP_DCR=off,CLOUDHAL_MCP_CLIENT_HOSTSandCLOUDHAL_MCP_REDIRECT_SCHEMEScontrol it on both runtimes, and the Docker compose file passes them through. The Phase 2 server-side test client (OauthServer.createClient) is removed.set_embargothrough an OAuth connection now files the gate for a person's approval instead of leaving it unapplied, and the request is notified while it waits.safeFetchresults carry the response headers.e6fe6eb: Studio shows "Connected agents" and how to connect an MCP client by URL (RFC-0044 Phase 3b). On
/agents, each member sees the apps they connected through OAuth. A client is named as the consent screen named it: a metadata document's host first, a self-registered client as not verified, a name that looks like a well-known client with a warning. Each row shows what the connection can do in words, its mode and when it was last used, and has Disconnect, which uses the existing revoke. Administrators see every member's connections under All keys. "Connect an MCP client" gains a Connect by URL tab: the deployment's/mcpURL, steps for Claude, Claude Code, ChatGPT and Codex, Cursor, VS Code and the MCP Inspector, and a note where a client needs dynamic client registration that is off.GET /api/agent-grantsnow returnsclient(kind, a document client'shost,lookalike) with the name sanitized, and with?all=1each owner'srole./api/instancereportsfeatures.mcpOauthClients: the/mcpresource, and whether metadata documents and dynamic registration are on. The new guide isdocs/guides/mcp-oauth.md, and the MCP server README has an Authentication section.Updated dependencies [6057871]
Updated dependencies [d363160]
Updated dependencies [e6fe6eb]
@cloudhal/cli@0.7.0
Minor Changes
mcp()andjwt()plugins run in the Studio's auth instance when the runtime has a stable public origin: the admin Worker uses its origin,cloudhal studioneeds--base-url/CLOUDHAL_BASE_URL(it logs why OAuth is off otherwise), andCLOUDHAL_MCP_OAUTH=offturns it off. Access tokens are Ed25519 JWTs bound to/mcpfor one hour, refresh tokens rotate with a 30-second reuse window, and each connection is approved on Studio's new consent screen (/oauth/consent), which narrows the requested scopes by the member's role and records anagent_grantsrow (migration0031_oauth). A token resolves to the same principal an agent key does; revoking a connection (DELETE /api/agent-grants/:id) or removing the member refuses it on its next call. The Better Auth family moves to 1.7.18. Client registration (CIMD, DCR) and the "Connected agents" screen follow in Phase 3.Patch Changes
d363160: Remote MCP clients can now register themselves (RFC-0044 Phase 3a, ADR-0045). Clients that name an HTTPS Client ID Metadata Document as their
client_id(Claude Code, Codex, VS Code) are accepted through@better-auth/cimd, fetched with the media import's SSRF-safe transport (pinned on Node, DoH-checked on Workers; https only, public addresses only, no redirects, 5 KB, 5 s). Clients without one (Cursor) use dynamic client registration at/api/auth/oauth2/register: public clients only, rate-limited per address and per day, capped at 5,000, and pruned by the scheduler after 30 unused days. Document clients are fetched at most hourly per client, with budgets in Cloudhal's own counters that never lock out stored clients, a cap of 5,000 that evicts unused clients (the well-known clients' hosts are exempt), pruning after three hours unused, and a failed refetch that refuses the client; migration0032_oauth_client_kind_indexindexes them. Redirect URIs must be https, loopback http (any port) or a native app's private-use scheme (cursor,vscode, reverse-domain,CLOUDHAL_MCP_REDIRECT_SCHEMES), and the client host list applies at every authorization. With DCR off, the clients it registered earlier cannot start new authorizations. The consent screen shows client names plain and short, a document client's host first, and marks self-registered clients as unverified.CLOUDHAL_MCP_CIMD=off,CLOUDHAL_MCP_DCR=off,CLOUDHAL_MCP_CLIENT_HOSTSandCLOUDHAL_MCP_REDIRECT_SCHEMEScontrol it on both runtimes, and the Docker compose file passes them through. The Phase 2 server-side test client (OauthServer.createClient) is removed.set_embargothrough an OAuth connection now files the gate for a person's approval instead of leaving it unapplied, and the request is notified while it waits.safeFetchresults carry the response headers.e6fe6eb: Studio shows "Connected agents" and how to connect an MCP client by URL (RFC-0044 Phase 3b). On
/agents, each member sees the apps they connected through OAuth. A client is named as the consent screen named it: a metadata document's host first, a self-registered client as not verified, a name that looks like a well-known client with a warning. Each row shows what the connection can do in words, its mode and when it was last used, and has Disconnect, which uses the existing revoke. Administrators see every member's connections under All keys. "Connect an MCP client" gains a Connect by URL tab: the deployment's/mcpURL, steps for Claude, Claude Code, ChatGPT and Codex, Cursor, VS Code and the MCP Inspector, and a note where a client needs dynamic client registration that is off.GET /api/agent-grantsnow returnsclient(kind, a document client'shost,lookalike) with the name sanitized, and with?all=1each owner'srole./api/instancereportsfeatures.mcpOauthClients: the/mcpresource, and whether metadata documents and dynamic registration are on. The new guide isdocs/guides/mcp-oauth.md, and the MCP server README has an Authentication section.Updated dependencies [6057871]
Updated dependencies [d363160]
Updated dependencies [e6fe6eb]
@cloudhal/cloudflare@0.7.0
Minor Changes
mcp()andjwt()plugins run in the Studio's auth instance when the runtime has a stable public origin: the admin Worker uses its origin,cloudhal studioneeds--base-url/CLOUDHAL_BASE_URL(it logs why OAuth is off otherwise), andCLOUDHAL_MCP_OAUTH=offturns it off. Access tokens are Ed25519 JWTs bound to/mcpfor one hour, refresh tokens rotate with a 30-second reuse window, and each connection is approved on Studio's new consent screen (/oauth/consent), which narrows the requested scopes by the member's role and records anagent_grantsrow (migration0031_oauth). A token resolves to the same principal an agent key does; revoking a connection (DELETE /api/agent-grants/:id) or removing the member refuses it on its next call. The Better Auth family moves to 1.7.18. Client registration (CIMD, DCR) and the "Connected agents" screen follow in Phase 3.Patch Changes
client_id(Claude Code, Codex, VS Code) are accepted through@better-auth/cimd, fetched with the media import's SSRF-safe transport (pinned on Node, DoH-checked on Workers; https only, public addresses only, no redirects, 5 KB, 5 s). Clients without one (Cursor) use dynamic client registration at/api/auth/oauth2/register: public clients only, rate-limited per address and per day, capped at 5,000, and pruned by the scheduler after 30 unused days. Document clients are fetched at most hourly per client, with budgets in Cloudhal's own counters that never lock out stored clients, a cap of 5,000 that evicts unused clients (the well-known clients' hosts are exempt), pruning after three hours unused, and a failed refetch that refuses the client; migration0032_oauth_client_kind_indexindexes them. Redirect URIs must be https, loopback http (any port) or a native app's private-use scheme (cursor,vscode, reverse-domain,CLOUDHAL_MCP_REDIRECT_SCHEMES), and the client host list applies at every authorization. With DCR off, the clients it registered earlier cannot start new authorizations. The consent screen shows client names plain and short, a document client's host first, and marks self-registered clients as unverified.CLOUDHAL_MCP_CIMD=off,CLOUDHAL_MCP_DCR=off,CLOUDHAL_MCP_CLIENT_HOSTSandCLOUDHAL_MCP_REDIRECT_SCHEMEScontrol it on both runtimes, and the Docker compose file passes them through. The Phase 2 server-side test client (OauthServer.createClient) is removed.set_embargothrough an OAuth connection now files the gate for a person's approval instead of leaving it unapplied, and the request is notified while it waits.safeFetchresults carry the response headers.@cloudhal/storage@0.7.0
Minor Changes
mcp()andjwt()plugins run in the Studio's auth instance when the runtime has a stable public origin: the admin Worker uses its origin,cloudhal studioneeds--base-url/CLOUDHAL_BASE_URL(it logs why OAuth is off otherwise), andCLOUDHAL_MCP_OAUTH=offturns it off. Access tokens are Ed25519 JWTs bound to/mcpfor one hour, refresh tokens rotate with a 30-second reuse window, and each connection is approved on Studio's new consent screen (/oauth/consent), which narrows the requested scopes by the member's role and records anagent_grantsrow (migration0031_oauth). A token resolves to the same principal an agent key does; revoking a connection (DELETE /api/agent-grants/:id) or removing the member refuses it on its next call. The Better Auth family moves to 1.7.18. Client registration (CIMD, DCR) and the "Connected agents" screen follow in Phase 3.Patch Changes
client_id(Claude Code, Codex, VS Code) are accepted through@better-auth/cimd, fetched with the media import's SSRF-safe transport (pinned on Node, DoH-checked on Workers; https only, public addresses only, no redirects, 5 KB, 5 s). Clients without one (Cursor) use dynamic client registration at/api/auth/oauth2/register: public clients only, rate-limited per address and per day, capped at 5,000, and pruned by the scheduler after 30 unused days. Document clients are fetched at most hourly per client, with budgets in Cloudhal's own counters that never lock out stored clients, a cap of 5,000 that evicts unused clients (the well-known clients' hosts are exempt), pruning after three hours unused, and a failed refetch that refuses the client; migration0032_oauth_client_kind_indexindexes them. Redirect URIs must be https, loopback http (any port) or a native app's private-use scheme (cursor,vscode, reverse-domain,CLOUDHAL_MCP_REDIRECT_SCHEMES), and the client host list applies at every authorization. With DCR off, the clients it registered earlier cannot start new authorizations. The consent screen shows client names plain and short, a document client's host first, and marks self-registered clients as unverified.CLOUDHAL_MCP_CIMD=off,CLOUDHAL_MCP_DCR=off,CLOUDHAL_MCP_CLIENT_HOSTSandCLOUDHAL_MCP_REDIRECT_SCHEMEScontrol it on both runtimes, and the Docker compose file passes them through. The Phase 2 server-side test client (OauthServer.createClient) is removed.set_embargothrough an OAuth connection now files the gate for a person's approval instead of leaving it unapplied, and the request is notified while it waits.safeFetchresults carry the response headers.@cloudhal/agent-runtime@0.7.0
Patch Changes
@cloudhal/analytics@0.7.0
Patch Changes
@cloudhal/astro-renderer@0.7.0
Patch Changes
@cloudhal/comments@0.7.0
Patch Changes
@cloudhal/core-ts@0.7.0
Patch Changes
client_id(Claude Code, Codex, VS Code) are accepted through@better-auth/cimd, fetched with the media import's SSRF-safe transport (pinned on Node, DoH-checked on Workers; https only, public addresses only, no redirects, 5 KB, 5 s). Clients without one (Cursor) use dynamic client registration at/api/auth/oauth2/register: public clients only, rate-limited per address and per day, capped at 5,000, and pruned by the scheduler after 30 unused days. Document clients are fetched at most hourly per client, with budgets in Cloudhal's own counters that never lock out stored clients, a cap of 5,000 that evicts unused clients (the well-known clients' hosts are exempt), pruning after three hours unused, and a failed refetch that refuses the client; migration0032_oauth_client_kind_indexindexes them. Redirect URIs must be https, loopback http (any port) or a native app's private-use scheme (cursor,vscode, reverse-domain,CLOUDHAL_MCP_REDIRECT_SCHEMES), and the client host list applies at every authorization. With DCR off, the clients it registered earlier cannot start new authorizations. The consent screen shows client names plain and short, a document client's host first, and marks self-registered clients as unverified.CLOUDHAL_MCP_CIMD=off,CLOUDHAL_MCP_DCR=off,CLOUDHAL_MCP_CLIENT_HOSTSandCLOUDHAL_MCP_REDIRECT_SCHEMEScontrol it on both runtimes, and the Docker compose file passes them through. The Phase 2 server-side test client (OauthServer.createClient) is removed.set_embargothrough an OAuth connection now files the gate for a person's approval instead of leaving it unapplied, and the request is notified while it waits.safeFetchresults carry the response headers.create-cloudhal@0.7.0
Patch Changes
@cloudhal/mcp-server@0.7.0
Patch Changes
d363160: Remote MCP clients can now register themselves (RFC-0044 Phase 3a, ADR-0045). Clients that name an HTTPS Client ID Metadata Document as their
client_id(Claude Code, Codex, VS Code) are accepted through@better-auth/cimd, fetched with the media import's SSRF-safe transport (pinned on Node, DoH-checked on Workers; https only, public addresses only, no redirects, 5 KB, 5 s). Clients without one (Cursor) use dynamic client registration at/api/auth/oauth2/register: public clients only, rate-limited per address and per day, capped at 5,000, and pruned by the scheduler after 30 unused days. Document clients are fetched at most hourly per client, with budgets in Cloudhal's own counters that never lock out stored clients, a cap of 5,000 that evicts unused clients (the well-known clients' hosts are exempt), pruning after three hours unused, and a failed refetch that refuses the client; migration0032_oauth_client_kind_indexindexes them. Redirect URIs must be https, loopback http (any port) or a native app's private-use scheme (cursor,vscode, reverse-domain,CLOUDHAL_MCP_REDIRECT_SCHEMES), and the client host list applies at every authorization. With DCR off, the clients it registered earlier cannot start new authorizations. The consent screen shows client names plain and short, a document client's host first, and marks self-registered clients as unverified.CLOUDHAL_MCP_CIMD=off,CLOUDHAL_MCP_DCR=off,CLOUDHAL_MCP_CLIENT_HOSTSandCLOUDHAL_MCP_REDIRECT_SCHEMEScontrol it on both runtimes, and the Docker compose file passes them through. The Phase 2 server-side test client (OauthServer.createClient) is removed.set_embargothrough an OAuth connection now files the gate for a person's approval instead of leaving it unapplied, and the request is notified while it waits.safeFetchresults carry the response headers.e6fe6eb: Studio shows "Connected agents" and how to connect an MCP client by URL (RFC-0044 Phase 3b). On
/agents, each member sees the apps they connected through OAuth. A client is named as the consent screen named it: a metadata document's host first, a self-registered client as not verified, a name that looks like a well-known client with a warning. Each row shows what the connection can do in words, its mode and when it was last used, and has Disconnect, which uses the existing revoke. Administrators see every member's connections under All keys. "Connect an MCP client" gains a Connect by URL tab: the deployment's/mcpURL, steps for Claude, Claude Code, ChatGPT and Codex, Cursor, VS Code and the MCP Inspector, and a note where a client needs dynamic client registration that is off.GET /api/agent-grantsnow returnsclient(kind, a document client'shost,lookalike) with the name sanitized, and with?all=1each owner'srole./api/instancereportsfeatures.mcpOauthClients: the/mcpresource, and whether metadata documents and dynamic registration are on. The new guide isdocs/guides/mcp-oauth.md, and the MCP server README has an Authentication section.Updated dependencies [6057871]
Updated dependencies [d363160]
@cloudhal/schedules@0.7.0
Patch Changes
@cloudhal/core-contracts@0.7.0
No changes in this release.