Skip to content

chore: version packages - #87

Merged
vinaypuppal merged 1 commit into
mainfrom
changeset-release/main
Oct 8, 2026
Merged

vinaypuppal merged 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 8, 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

@perspective-ai/sdk@1.16.0

Minor Changes

  • aeff765: Make the embed script safe to load from Google Tag Manager. Calls queued on a Perspective stub before the script arrives are replayed, and Perspective(...) stays callable afterwards alongside the existing methods. Evaluating the script again replays any new queue and re-runs auto-init instead of no-oping. An embed whose container — or the marker a float or fullpage was mounted from — has left the document is destroyed and remounted, including after an SPA history change.

    Embeds now push lifecycle events to the page's dataLayer: perspective_widget_open, perspective_widget_ready, perspective_conversation_started, perspective_conversation_completed and perspective_widget_close. This applies to every build — the script tag, the npm package and @perspective-ai/sdk-react — whenever window.dataLayer already exists, as it does on most sites running Google Tag Manager. window.dataLayer is not created unless configure({ dataLayer: true }).

    If your site already pushes its own Perspective events (from onSubmit / onReady callbacks, or a Custom HTML tag that listens for perspective:* messages), remove that code or call configure({ dataLayer: false }) when you upgrade, or those conversions will be counted twice. To opt out a single embed, use data-perspective-datalayer="false" on a script-tag embed, or pass dataLayer: false in its config — to createWidget, openPopup and the other constructors, or as a prop to the React components and hooks.

Patch Changes

  • 0c89f81: Fix an unhandled InvalidStateError ("Closed before resume completed") on host pages when the float bubble unmounts while its welcome chime is still waiting on the browser to resume audio, such as on a client-side navigation to a page without the bubble.

@perspective-ai/sdk-react@1.16.0

Minor Changes

  • aeff765: Make the embed script safe to load from Google Tag Manager. Calls queued on a Perspective stub before the script arrives are replayed, and Perspective(...) stays callable afterwards alongside the existing methods. Evaluating the script again replays any new queue and re-runs auto-init instead of no-oping. An embed whose container — or the marker a float or fullpage was mounted from — has left the document is destroyed and remounted, including after an SPA history change.

    Embeds now push lifecycle events to the page's dataLayer: perspective_widget_open, perspective_widget_ready, perspective_conversation_started, perspective_conversation_completed and perspective_widget_close. This applies to every build — the script tag, the npm package and @perspective-ai/sdk-react — whenever window.dataLayer already exists, as it does on most sites running Google Tag Manager. window.dataLayer is not created unless configure({ dataLayer: true }).

    If your site already pushes its own Perspective events (from onSubmit / onReady callbacks, or a Custom HTML tag that listens for perspective:* messages), remove that code or call configure({ dataLayer: false }) when you upgrade, or those conversions will be counted twice. To opt out a single embed, use data-perspective-datalayer="false" on a script-tag embed, or pass dataLayer: false in its config — to createWidget, openPopup and the other constructors, or as a prop to the React components and hooks.

Patch Changes

  • Updated dependencies [0c89f81]
  • Updated dependencies [aeff765]
    • @perspective-ai/sdk@1.16.0

@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 56cc701 to 5e194b5 Compare October 8, 2026 14:54
@vinaypuppal
vinaypuppal merged commit 4bf34e1 into main Oct 8, 2026
5 checks passed
@vinaypuppal
vinaypuppal deleted the changeset-release/main branch October 8, 2026 15:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant