Skip to content

v5.0.0

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 04 Sep 11:22
· 10 commits to main since this release
Immutable release. Only release title and notes can be modified.
v5.0.0
53b8b92
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

@frontman/bindings

Patch Changes

  • #1620 17ca764 Thanks @BlueHotDog! - Use Node path.relative for relative path display and reject out-of-root search paths instead of falling back to the source root.

@frontman-ai/client

Minor Changes

  • #1496 f5f2b9b Thanks @kevin-ho! - Add Custom Providers to Settings so users can configure per-user, publicly reachable OpenAI-compatible providers. Providers save their model IDs atomically, support optional API keys, reject stale updates, and appear as model-picker groups once configured. Outbound requests resolve and pin public destinations before connecting.

  • #1559 d64a09c Thanks @uinstinct! - Add an execute control to element annotations: Ctrl/Cmd+Enter or the send button sends the selected elements and comments through the chatbox flow.

  • #1538 76efaeb Thanks @uinstinct! - Add the ability to remove a queued message before the agent picks it up. Each row in the queued-messages drawer now has a remove button, which deletes the pending message server-side.

Patch Changes

  • #1564 2424a52 Thanks @BlueHotDog! - Require every final agent response to include a concise TL;DR covering outcomes and relevant next steps.

  • #1598 1516deb Thanks @BlueHotDog! - Show the five most recent tasks in the empty chat starter so users can resume previous work.

  • #1589 373d94e Thanks @BlueHotDog! - Make the embedded Frontman approval popup clearer for non-technical users by explaining why it appears, what access is granted, and when to allow it.

  • #1589 373d94e Thanks @BlueHotDog! - Complete embedded bearer-token authentication for client sockets, remove the legacy socket-token path, and disable credentialed API CORS.

  • #1573 0e7830c Thanks @uinstinct! - Pressing Escape while the element inspector is active now closes the open comment popup, then clears all selected elements, and finally exits selection mode when nothing is selected.

  • #1589 373d94e Thanks @BlueHotDog! - Prevent the app from crashing when an existing loaded task was created before completed file-change snapshots were added.

  • #1562 35726d0 Thanks @BlueHotDog! - Keep task channels alive when MCP tools return audio, resource links, or embedded resources by reporting unsupported content as tool errors.

  • #1561 e0fc341 Thanks @BlueHotDog! - Reject MCP catalogs containing duplicate tool names before publishing any discovered tools.

  • #1566 efb4fbf Thanks @BlueHotDog! - Remove unused ACP, MCP, and relay progress observers so diagnostic callbacks cannot interrupt protocol delivery.

  • #1556 45b62c4 Thanks @BlueHotDog! - Prevent message submission until a model is selected.

  • #1594 033e90f Thanks @BlueHotDog! - Track first-task feedback dialog impressions, closes, share clicks, and Discord clicks in Heap.

  • #1599 991732d Thanks @dependabot! - Update Tiptap core to 3.30.4.

@frontman-ai/astro

Major Changes

  • #1590 77fb937 Thanks @BlueHotDog! - Preserve official MCP tool, content annotation, and implementation metadata through relay boundaries. Relay tools now require protocol version 2.0 and the MCP _meta["ai.frontman/tool-metadata"] shape instead of legacy top-level metadata fields.

Minor Changes

  • #1617 5782bd7 Thanks @BlueHotDog! - Enrich get_client_pages with Astro route pathname, segments, redirect metadata, fallback routes, and serialized route regex details.

Patch Changes

  • #1601 b447a4a Thanks @BlueHotDog! - Add get_resolved_astro_config so Astro agents can inspect sanitized resolved config before routing, rendering, adapter, i18n, image, Markdown, redirect, session, security, or deployment changes.

@frontman-ai/frontman-client

Major Changes

  • #1590 77fb937 Thanks @BlueHotDog! - Preserve official MCP tool, content annotation, and implementation metadata through relay boundaries. Relay tools now require protocol version 2.0 and the MCP _meta["ai.frontman/tool-metadata"] shape instead of legacy top-level metadata fields.

Patch Changes

  • #1622 0bc42d9 Thanks @BlueHotDog! - Handle ACP Phoenix push replies and clean up failed initialize connections after request timeouts.

  • #1589 373d94e Thanks @BlueHotDog! - Complete embedded bearer-token authentication for client sockets, remove the legacy socket-token path, and disable credentialed API CORS.

  • #1619 e2cd5a0 Thanks @BlueHotDog! - Reject ACP client requests after a timeout instead of leaving the UI stuck when the server never responds.

  • #1566 efb4fbf Thanks @BlueHotDog! - Remove unused ACP, MCP, and relay progress observers so diagnostic callbacks cannot interrupt protocol delivery.

  • #1557 0c813c5 Thanks @BlueHotDog! - Preserve integral JSON-RPC numeric IDs above signed 32-bit range.

@frontman-ai/frontman-core

Major Changes

  • #1590 77fb937 Thanks @BlueHotDog! - Preserve official MCP tool, content annotation, and implementation metadata through relay boundaries. Relay tools now require protocol version 2.0 and the MCP _meta["ai.frontman/tool-metadata"] shape instead of legacy top-level metadata fields.

Patch Changes

  • #1621 361d5c9 Thanks @BlueHotDog! - Keep path recovery scoped when source roots are relative.

  • #1620 17ca764 Thanks @BlueHotDog! - Use Node path.relative for relative path display and reject out-of-root search paths instead of falling back to the source root.

  • #1566 efb4fbf Thanks @BlueHotDog! - Remove unused ACP, MCP, and relay progress observers so diagnostic callbacks cannot interrupt protocol delivery.

  • Updated dependencies [77fb937, 17ca764, efb4fbf, 0c813c5]:

    • @frontman-ai/frontman-protocol@4.0.0
    • @frontman/bindings@0.3.2

@frontman-ai/nextjs

Major Changes

  • #1590 77fb937 Thanks @BlueHotDog! - Preserve official MCP tool, content annotation, and implementation metadata through relay boundaries. Relay tools now require protocol version 2.0 and the MCP _meta["ai.frontman/tool-metadata"] shape instead of legacy top-level metadata fields.

Minor Changes

  • #1496 f5f2b9b Thanks @kevin-ho! - Add Custom Providers to Settings so users can configure per-user, publicly reachable OpenAI-compatible providers. Providers save their model IDs atomically, support optional API keys, reject stale updates, and appear as model-picker groups once configured. Outbound requests resolve and pin public destinations before connecting.

Patch Changes

  • #1572 45c9872 Thanks @BlueHotDog! - Fail closed for Next.js Frontman routes outside development unless explicitly enabled with FRONTMAN_ENABLE_IN_PRODUCTION=1 or FRONTMAN_ENABLED=1.

  • #1574 7a2776a Thanks @BlueHotDog! - Fix generated instrumentation type resolution during Next.js production builds and add a CI compatibility matrix for packed Next.js consumers.

@frontman-ai/frontman-preview-bridge

Patch Changes

@frontman-ai/frontman-protocol

Major Changes

  • #1590 77fb937 Thanks @BlueHotDog! - Preserve official MCP tool, content annotation, and implementation metadata through relay boundaries. Relay tools now require protocol version 2.0 and the MCP _meta["ai.frontman/tool-metadata"] shape instead of legacy top-level metadata fields.

Patch Changes

  • #1566 efb4fbf Thanks @BlueHotDog! - Remove unused ACP, MCP, and relay progress observers so diagnostic callbacks cannot interrupt protocol delivery.

  • #1557 0c813c5 Thanks @BlueHotDog! - Preserve integral JSON-RPC numeric IDs above signed 32-bit range.

@frontman-ai/vite

Major Changes

  • #1590 77fb937 Thanks @BlueHotDog! - Preserve official MCP tool, content annotation, and implementation metadata through relay boundaries. Relay tools now require protocol version 2.0 and the MCP _meta["ai.frontman/tool-metadata"] shape instead of legacy top-level metadata fields.
Assets 5
Loading