Skip to content

v5.5.0

Choose a tag to compare

@github-actions github-actions released this 26 Oct 19:51
· 83 commits to main since this release
Immutable release. Only release title and notes can be modified.
095f902

@frontman/bindings

Patch Changes

  • #1972 9dedf54 Thanks @BlueHotDog! - Handle cross-origin preview navigation without WindowProxy option errors. Reload and address-bar navigation now reset the iframe from parent state, and preview tools reject stale documents until a supported page loads.

@frontman-ai/client

Patch Changes

  • #2002 af7e347 Thanks @BlueHotDog! - Block new prompts as soon as a trial is canceled, including cancellations scheduled for trial end. Keep unused free prompts available and preserve paid subscription access.

    Show canceled trial access accurately in billing settings instead of promising access until the scheduled cancellation date.

  • #1993 c2535b8 Thanks @BlueHotDog! - Show todo progress with a static started-but-unfinished indicator instead of a spinner. Rename the plan heading to "Plan" so stopped agents do not appear active. Preserve todo statuses after Stop.

  • #1972 9dedf54 Thanks @BlueHotDog! - Handle cross-origin preview navigation without WindowProxy option errors. Reload and address-bar navigation now reset the iframe from parent state, and preview tools reject stale documents until a supported page loads.

  • #1985 f9894b0 Thanks @dependabot! - Update lucide-react from 1.46.0 to 1.48.0.

  • #1975 08b834a Thanks @dependabot! - Update @pierre/diffs from 1.4.2 to 1.5.1.

@frontman-ai/astro

Patch Changes

@frontman-ai/frontman-client

Patch Changes

  • #1919 db72760 Thanks @BlueHotDog! - Use a shared typed record for relay tool definitions. Tool names are required strings, and callers no longer decode them from JSON.

    Preserve vendor metadata and JSON Schema extensions. Unknown top-level tool fields are no longer forwarded.

  • #1980 a21ed02 Thanks @dependabot! - Update the Phoenix JavaScript client from 1.8.14 to 1.8.15.

  • #1974 51c42f6 Thanks @dependabot! - Update the Sentry browser SDK from 10.74.0 to 11.0.0.

@frontman-ai/frontman-core

Patch Changes

  • #1919 db72760 Thanks @BlueHotDog! - Use a shared typed record for relay tool definitions. Tool names are required strings, and callers no longer decode them from JSON.

    Preserve vendor metadata and JSON Schema extensions. Unknown top-level tool fields are no longer forwarded.

  • Updated dependencies [9dedf54, db72760]:

    • @frontman/bindings@0.3.4
    • @frontman-ai/frontman-protocol@4.1.2

@frontman-ai/nextjs

Patch Changes

  • #1919 db72760 Thanks @BlueHotDog! - Use a shared typed record for relay tool definitions. Tool names are required strings, and callers no longer decode them from JSON.

    Preserve vendor metadata and JSON Schema extensions. Unknown top-level tool fields are no longer forwarded.

  • #1960 b60a406 Thanks @dependabot! - Update the Sentry Next.js SDK to 10.75.2 for upstream telemetry fixes.

  • #1983 b0f2944 Thanks @dependabot! - Update the Sentry Next.js SDK from 10.75.2 to 11.0.0.

@frontman-ai/frontman-preview-bridge

Patch Changes

  • Updated dependencies [9dedf54, db72760]:
    • @frontman/bindings@0.3.4
    • @frontman-ai/frontman-protocol@4.1.2
    • @frontman-ai/astro-browser@0.3.0

@frontman-ai/frontman-protocol

Patch Changes

  • #1919 db72760 Thanks @BlueHotDog! - Use a shared typed record for relay tool definitions. Tool names are required strings, and callers no longer decode them from JSON.

    Preserve vendor metadata and JSON Schema extensions. Unknown top-level tool fields are no longer forwarded.

@frontman-ai/frontman-wordpress

Minor Changes

  • #2001 677414f Thanks @BlueHotDog! - Add exact-fragment editing to wp_update_post for user-authorized changes to draft, freeform HTML, and block HTML posts. Readbacks include a content SHA256 hash. Edit mode requires a fresh hash and one unique exact-text anchor, preserves surrounding bytes and omitted fields, and reuses existing save permissions and verification. Conflict detection is best-effort, not atomic.

Patch Changes

  • #1840 e59b88d Thanks @BlueHotDog! - Prepare WordPress for gradual preview bridge rollout. Package a same-origin page-context bridge and declare page-context-v1 support on the Frontman runtime-config element. The bridge stays inactive with existing clients, and prompt submission remains unchanged. Load it in the footer and include bundled dependency license notices.

  • #1971 7993341 Thanks @BlueHotDog! - Clarify that wp_update_option supports only allowlisted core WordPress options, not arbitrary plugin-private options.

  • #1944 f906abf Thanks @BlueHotDog! - Add approved creation of WebFactory 301 Redirects rules with duplicate checks and storage preservation checks across all pages.
    Normalize site-relative destinations when the site URL ends with a slash.

  • #1945 d2b8e49 Thanks @BlueHotDog! - Add approved deletion of WebFactory 301 Redirects rules with exact source and row checks.
    Verify preservation of every remaining rule, including rules beyond the first page.

  • #1995 8bcc28f Thanks @BlueHotDog! - Add opt-in stored layout context to Elementor site-wide text search. Return each matched element's parent, sibling position, nearest layout ancestor, and narrow stored style overrides without changing matches or candidate pagination. Reject ambiguous element IDs only when context is requested. Stored overrides and unresolved global references are not computed styles.

  • #1995 8bcc28f Thanks @BlueHotDog! - Generate missing IDs recursively when adding or generating new Elementor subtrees. Preserve supplied IDs, reject malformed children and ID collisions before saving, and report the input path that needs repair.

  • #1946 781935f Thanks @BlueHotDog! - Verify WebFactory 301 Redirects and Redirection coexistence with a focused WordPress runtime suite.

  • #1941 812ec30 Thanks @BlueHotDog! - Reject duplicate WordPress tool names instead of silently replacing an existing handler.

  • #1943 4f229cf Thanks @BlueHotDog! - WebFactory 301 Redirects now validates literal source paths and safe HTTP(S) destinations.
    Absolute destinations use the same path restrictions as site-relative destinations.

  • #1947 b3f4e0f Thanks @BlueHotDog! - Verify WebFactory redirect HTTP behavior, plugin identity, and database failure boundaries.

  • #1942 1247208 Thanks @BlueHotDog! - Expose the pinned WebFactory 301 Redirects store separately from Redirection.

  • #1941 812ec30 Thanks @BlueHotDog! - Report unexpected initialization, request-dispatch, and deferred UI and diagnostics admin callback failures when PHP diagnostics are enabled, while preserving WordPress hook contracts and error handling.

  • #1965 1d6c378 Thanks @BlueHotDog! - Add opt-in installation paths to wp_get_site_info for read-only location checks. Keep paths out of default results and preserve administrator-only access. Report the configured WordPress root and its resolved path without exposing general filesystem tools.

  • #1954 9d4b474 Thanks @BlueHotDog! - Read and update one Yoast Free focus keyphrase through the existing guarded provider path, including sanitization, permissions, clearing, and stored readback.

  • #1953 fccc78e Thanks @BlueHotDog! - Use one field map for Yoast metadata validation, permissions, provider operations, and stored snapshots without changing tool behavior.

  • #1952 fd3afc9 Thanks @BlueHotDog! - Allow Yoast SEO Free title and description tools when the required runtime capabilities are available, instead of requiring an exact version match. Preserve provider writes, sanitization, conflict checks, permissions, and stored readback. Add Yoast 28.6 to the pinned integration-test matrix.