Skip to content

chore: version packages - #9361

Merged
speakeasy-approvals[bot] merged 1 commit into
mainfrom
changeset-release/main
Nov 21, 2026
Merged

speakeasy-approvals[bot] merged 1 commit into
mainfrom
changeset-release/main

Conversation

@gram-bot

@gram-bot gram-bot Bot commented Nov 20, 2026 •

Copy link
Copy Markdown
Contributor

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

dashboard@0.153.0

Minor Changes

  • 2a23053: Roles & Permissions has an Access Requests tab listing members' pending requests. Reviewing one, or opening it from the email or Slack link, lets an administrator approve it for 1, 2 or 4 hours or until the end of the day, deny it, or assign a role. A member who has asked sees their request as pending on the page they were blocked on, and access that can't be given temporarily tells them to ask an administrator instead.

Patch Changes

  • a62cd80: A member waiting on an access request now sees the page open up as soon as an administrator decides it, wherever they asked: a banner, the popover on a disabled button such as Create MCP server, or a full page. Previously, closing the popover stopped the check until the page was reloaded.
  • b1c1e0c: An agent's MCP sign-in tab no longer marks every personal server "Could not check connection" for an admin previewing roles: reading an agent's attached connections now follows the same permission check as the rest of the agent's pages. A viewer who may not see the agent's attached connection is told so plainly, and that server is no longer counted on the tab.
  • a6fc982: keys.list can now return one page at a time. Send limit (1 to 100) to get a page, then pass the returned next_cursor as cursor to get the next one. Keys come newest first. Send search to only return keys whose name contains that text, ignoring case. Callers that send no limit still get every key in one response, as before. The dashboard's API Keys page now loads 50 keys at a time with a "Load more" button and searches on the server, so it stays fast for organizations with thousands of keys.
  • 427498d: Setting up Enterprise Managed Auth on an MCP Authentication Provider now asks for one thing: the identity provider's issuer URL. "Set up EMA" opens the field in place, with no choice between providers and no trip to the Okta page. An Okta org URL such as https://acme.okta.com works, and a pasted Okta admin console URL is read as the org URL.
  • 07717cf: On an MCP server's Team access page, giving someone connect access to a set of tool annotations, such as "Read-only", now works when they hold no connect access yet. The choice used to save as blocks on the other annotations only, which left the person with no access at all.
  • 95c9bbb: The MCP server Overview keeps its labels while usage loads, so only the figures shimmer, and coming back to the tab within a few minutes shows the last figures at once instead of reloading them.
  • e01f674: Changing the time range on the MCP server Overview shows the loading state in the top-tools lists until the new range arrives, instead of the previous range's tools.
  • a92b906: The dashboard no longer records screen sessions. PostHog session recording and Datadog session replay are switched off, and the Claire de Fermat tracking pixel is removed. Product analytics events and Datadog performance and error monitoring are unchanged.
  • cba49d7: Opening an MCP server's pages no longer creates a client session for the viewer. The readiness check only asks an issuer-gated server whether it answers after you connect your account in Inspect.
  • 8e5b454: Access requests can now be stored and decided. With the access requests rollout on, requesting access records a pending request that an organization administrator can approve as a temporary grant or deny, through the new listAccessRequests, decideAccessRequest and withdrawAccessRequest endpoints. Scopes that cannot be given temporarily can no longer be requested while the rollout is on. Administrators are still emailed.
  • b93dd41: A tool with no annotations is now classified as unannotated. A rule with no annotation limit still covers it, a rule limited to read-only tools no longer does, and a tool that says it is both read-only and destructive is treated as destructive. The access, agents and Platform MCP APIs accept unannotated as a rule's annotation, and the role editor classifies tools the same way the server does and keeps a rule's unannotated selectors when another annotation is edited.

server@2.39.0

Minor Changes

  • 87acb73: Organization administrators now get a Slack DM for each access request, with a menu to pick how long the access lasts (1, 2 or 4 hours or until the end of the requester's day), an Allow button and a Deny button. Every card is updated with the outcome, and the requester is told by DM when their request is approved, denied or expires.
  • a6fc982: keys.list can now return one page at a time. Send limit (1 to 100) to get a page, then pass the returned next_cursor as cursor to get the next one. Keys come newest first. Send search to only return keys whose name contains that text, ignoring case. Callers that send no limit still get every key in one response, as before. The dashboard's API Keys page now loads 50 keys at a time with a "Load more" button and searches on the server, so it stays fast for organizations with thousands of keys.
  • 8e5b454: Access requests can now be stored and decided. With the access requests rollout on, requesting access records a pending request that an organization administrator can approve as a temporary grant or deny, through the new listAccessRequests, decideAccessRequest and withdrawAccessRequest endpoints. Scopes that cannot be given temporarily can no longer be requested while the rollout is on. Administrators are still emailed.

Patch Changes

  • b1c1e0c: An agent's MCP sign-in tab no longer marks every personal server "Could not check connection" for an admin previewing roles: reading an agent's attached connections now follows the same permission check as the rest of the agent's pages. A viewer who may not see the agent's attached connection is told so plainly, and that server is no longer counted on the tab.
  • 161c16c: Acknowledge deliveries to deleted webhook triggers without processing them, preventing Slack retries and noisy error logs.
  • 265e38b: An Enterprise Managed Auth sign-in to a gateway no longer fails when one of the gateway's servers isn't connected yet. The session is issued for the servers that are ready, and calling a server that isn't connected returns a link to its connect page. After connecting, the app picks the server up the next time it signs in to the gateway. Sign-ins to a single MCP server still fail until it is connected.
  • 118268a: A permission check on an organization other than the one the caller is acting in is now always refused.
  • 2bacdc5: A risk policy now applies when the caller's permissions cannot be read or the policy cannot be evaluated. Before, such a failure left the request unchecked. A policy is skipped only when the caller is outside its audience or holds an exemption.
  • 33f26df: A permission grant limited to a value the request does not carry no longer matches it. Connecting to a server still matches a grant limited to some tools, and a refusal caused by a missing value is logged.
  • 56828b2: Tool and annotation limits now apply to using an MCP server only. A view or manage rule, or a block on either, that names tools or annotations is refused when saved.
  • 8429f32: Tool Logs filtered by user email, user id or external user id load much faster. These filters are now answered from the per-trace summaries instead of a scan of every raw log row, which could time out.
  • b93dd41: A tool with no annotations is now classified as unannotated. A rule with no annotation limit still covers it, a rule limited to read-only tools no longer does, and a tool that says it is both read-only and destructive is treated as destructive. The access, agents and Platform MCP APIs accept unannotated as a rule's annotation, and the role editor classifies tools the same way the server does and keeps a rule's unannotated selectors when another annotation is edited.

@gram-bot
gram-bot Bot requested review from a team as code owners November 20, 2026 07:54
@gram-bot
gram-bot Bot force-pushed the changeset-release/main branch 28 times, most recently from 3817eaa to d77e9a7 Compare November 20, 2026 16:44
@gram-bot
gram-bot Bot force-pushed the changeset-release/main branch 18 times, most recently from 86d73ef to 8f2bd5d Compare November 21, 2026 01:41
@gram-bot
gram-bot Bot force-pushed the changeset-release/main branch from 8f2bd5d to be28f55 Compare November 21, 2026 02:02

@speakeasy-approvals speakeasy-approvals Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Scheduled release approval. Required checks are green on be28f55.

@speakeasy-approvals
speakeasy-approvals Bot added this pull request to the merge queue Nov 21, 2026
Merged via the queue into main with commit 74d4861 Nov 21, 2026
55 checks passed
@speakeasy-approvals
speakeasy-approvals Bot deleted the changeset-release/main branch November 21, 2026 04:08
@github-actions github-actions Bot locked and limited conversation to collaborators Nov 21, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants