You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@hamilton.apache.org by "dependabot[bot] (via GitHub)" <gi...@apache.org> on 2026/06/16 12:45:26 UTC
[PR] Bump @opentelemetry/core and posthog-js in /ui/frontend [hamilton]
dependabot[bot] opened a new pull request, #1636:
URL: https://github.com/apache/hamilton/pull/1636
Removes [@opentelemetry/core](https://github.com/open-telemetry/opentelemetry-js). It's no longer used after updating ancestor dependency [posthog-js](https://github.com/PostHog/posthog-js). These dependencies need to be updated together.
Removes `@opentelemetry/core`
Updates `posthog-js` from 1.352.0 to 1.386.8
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/PostHog/posthog-js/releases">posthog-js's releases</a>.</em></p>
<blockquote>
<h2>posthog-js@1.386.8</h2>
<h2>1.386.8</h2>
<h3>Patch Changes</h3>
<ul>
<li><a href="https://redirect.github.com/PostHog/posthog-js/pull/3838">#3838</a> <a href="https://github.com/PostHog/posthog-js/commit/3094f733bfda34b09b5bc14ad919898b95a189f3"><code>3094f73</code></a> Thanks <a href="https://github.com/TueHaulund"><code>@TueHaulund</code></a>! - fix(replay): discard the prior session's buffer when start() bails out a pending stop(). On a stopSessionRecording() → reset() → identify(newUser) → startSessionRecording() sequence, stopSessionRecording() takes the async compression-drain path, deferring its buffer flush and teardown. start() correctly invalidates that pending cleanup so the new recorder survives, but it left the stopped session's snapshot buffer in place. The re-entrant session-id restart then flushed those previous-user snapshots under the OLD session id, producing a mixed-distinct_id session that server-side <code>any(distinct_id)</code> attribution resolves to the wrong person — recordings showing the previous user's ident
ity. start() now clears that stale buffer alongside invalidating the compression queue, matching the drop-trailing-data trade-off the bailed-out stop() path already accepts.
(2026-06-15)</li>
</ul>
<h2>posthog-js@1.386.7</h2>
<h2>1.386.7</h2>
<h3>Patch Changes</h3>
<ul>
<li>
<p><a href="https://redirect.github.com/PostHog/posthog-js/pull/3837">#3837</a> <a href="https://github.com/PostHog/posthog-js/commit/29bf8e386a4050531e9cfd906c33b75945fcb6ad"><code>29bf8e3</code></a> Thanks <a href="https://github.com/marandaneto"><code>@marandaneto</code></a>! - Add missing bugs metadata to package manifests.
(2026-06-15)</p>
</li>
<li>
<p><a href="https://redirect.github.com/PostHog/posthog-js/pull/3832">#3832</a> <a href="https://github.com/PostHog/posthog-js/commit/d3a9462b8b21994764bdd2802973d82ffe472294"><code>d3a9462</code></a> Thanks <a href="https://github.com/archievi"><code>@archievi</code></a>! - Surveys: guard the remaining unprotected <code>localStorage</code> accesses (<code>reset()</code> and the <code>lastSeenSurveyDate</code> write) so a <code>SecurityError</code> in cross-origin iframes is swallowed instead of bubbling up to user monitoring.
(2026-06-15)</p>
</li>
<li>
<p>Updated dependencies [<a href="https://github.com/PostHog/posthog-js/commit/29bf8e386a4050531e9cfd906c33b75945fcb6ad"><code>29bf8e3</code></a>]:</p>
<ul>
<li><code>@posthog/core</code><a href="https://github.com/1"><code>@1</code></a>.32.4</li>
<li><code>@posthog/types</code><a href="https://github.com/1"><code>@1</code></a>.386.4</li>
</ul>
</li>
</ul>
<h2>posthog-js@1.386.6</h2>
<h2>1.386.6</h2>
<h3>Patch Changes</h3>
<ul>
<li>
<p><a href="https://redirect.github.com/PostHog/posthog-js/pull/3804">#3804</a> <a href="https://github.com/PostHog/posthog-js/commit/a27b16305eaef7fa8b4b36e6d2ffff1dbec7ba6b"><code>a27b163</code></a> Thanks <a href="https://github.com/pauldambra"><code>@pauldambra</code></a>! - fix(product-tours): drop the cached tours blob when product tours is not enabled</p>
<p>Tours fetched while product tours was enabled are cached under <code>ph_product_tours</code> in the main persistence blob. Once product tours is disabled (remote config or the <code>disable_product_tours</code> option) that cache was never cleaned up, so a potentially large stale blob kept riding on every persistence write — and on every cross-tab <code>storage</code> event those writes broadcast. <code>onRemoteConfig</code> now clears the cached tours whenever product tours resolves to disabled; they are re-fetched if it is ever re-enabled. (2026-06-11)</p>
</li>
</ul>
<h2>posthog-js@1.386.5</h2>
<h2>1.386.5</h2>
<h3>Patch Changes</h3>
<ul>
<li><a href="https://redirect.github.com/PostHog/posthog-js/pull/3801">#3801</a> <a href="https://github.com/PostHog/posthog-js/commit/bd06ac7c09f48dc31b3019525561536452297b8d"><code>bd06ac7</code></a> Thanks <a href="https://github.com/ksvat"><code>@ksvat</code></a>! - fix(replay): prevent silent recorder teardown on session-id rotation. When the session id rotates during active rrweb capture, <code>_updateWindowAndSessionIds</code> calls <code>stop()</code> then synchronously <code>start('session_id_changed')</code>. If <code>stop()</code> took the <code>_stopAfterCompressionQueueDrains</code> path (which fires whenever the compression queue is non-empty — common during steady recording), its async cleanup would later resolve and call <code>_teardown()</code> against the freshly-started recorder, stopping rrweb, removing event listeners, and emptying the V2 trigger-group matchers. From that point on, the recorder's <code>status</code> getter kept reporting <code>active</cod
e>/<code>sampled</code> (the <code>_strategy</code> reference was still set), but rrweb was no longer producing events, no listeners were registered, and no <code>$snapshot</code> data reached the server — the session looked recording-eligible from event metadata yet produced no replay. <code>start()</code> now invalidates the compression-queue state (generation bump plus reset of the stop-in-progress flag and queued-event count), so any pending cleanup from a prior <code>stop()</code> bails at its existing generation check and a later <code>stop()</code> of the new recorder is not mistaken for the old in-progress one. Affects long-running tabs that rotate session id mid-use (idle timeout, session-past-max-length, or <code>posthog.reset()</code>).
(2026-06-11)</li>
</ul>
<h2>posthog-js@1.386.4</h2>
<h2>1.386.4</h2>
<h3>Patch Changes</h3>
<ul>
<li><a href="https://redirect.github.com/PostHog/posthog-js/pull/3767">#3767</a> <a href="https://github.com/PostHog/posthog-js/commit/fdc07f32f886602504d7c1132adfbcccdb4112ec"><code>fdc07f3</code></a> Thanks <a href="https://github.com/arnohillen"><code>@arnohillen</code></a>! - replay: jump scrolls instantly when seeking past pages that use <code>scroll-behavior: smooth</code>. During fast-forward the replayer applied scrolls with <code>behavior: 'auto'</code>, which inherits the page's CSS <code>scroll-behavior</code> — so on sites that set <code>scroll-behavior: smooth</code> (e.g. Silk bottom sheets/modals) a seeked scroll animated from 0 instead of jumping, leaving scroll-revealed content (the open sheet) out of view and showing only the backdrop until the animation caught up. Sync scrolls now use <code>behavior: 'instant'</code>, matching the method's stated intent that smooth scrolling be disabled while fast-forwarding. Full snapshot rebuilds apply their initial offse
t with <code>behavior: 'instant'</code> too, so the document-level scroll doesn't animate either.
(2026-06-11)</li>
</ul>
<h2>posthog-js@1.386.3</h2>
<h2>1.386.3</h2>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/PostHog/posthog-js/commit/c8269541d4cc927bfc5a4d651520564f97d42d4f"><code>c826954</code></a> chore: update versions and lockfile [version bump]</li>
<li><a href="https://github.com/PostHog/posthog-js/commit/3094f733bfda34b09b5bc14ad919898b95a189f3"><code>3094f73</code></a> fix(replay): discard prior session buffer on restart across reset (<a href="https://redirect.github.com/PostHog/posthog-js/issues/3838">#3838</a>)</li>
<li><a href="https://github.com/PostHog/posthog-js/commit/47aea13be9b6a9c61f7ef16fb683adc7a669a37f"><code>47aea13</code></a> chore: update versions and lockfile [version bump]</li>
<li><a href="https://github.com/PostHog/posthog-js/commit/29bf8e386a4050531e9cfd906c33b75945fcb6ad"><code>29bf8e3</code></a> fix: add missing bugs metadata (<a href="https://redirect.github.com/PostHog/posthog-js/issues/3837">#3837</a>)</li>
<li><a href="https://github.com/PostHog/posthog-js/commit/d3a9462b8b21994764bdd2802973d82ffe472294"><code>d3a9462</code></a> fix: Guard remaining survey localStorage accesses against SecurityError (<a href="https://redirect.github.com/PostHog/posthog-js/issues/358">#358</a>...</li>
<li><a href="https://github.com/PostHog/posthog-js/commit/a3eff2731e92b5f6e359a8c583d5a39c94863a13"><code>a3eff27</code></a> chore(deps): bump turbo to 2.9.16 (<a href="https://redirect.github.com/PostHog/posthog-js/issues/3836">#3836</a>)</li>
<li><a href="https://github.com/PostHog/posthog-js/commit/5e8c4b7ea432290621296c64ce19ad44ef163f9b"><code>5e8c4b7</code></a> chore: update versions and lockfile [version bump]</li>
<li><a href="https://github.com/PostHog/posthog-js/commit/d6fc0a50fa2c2650869e3444a030533753ff0b4f"><code>d6fc0a5</code></a> feat(flags): support early_exit in posthog-node local evaluation (<a href="https://redirect.github.com/PostHog/posthog-js/issues/3705">#3705</a>)</li>
<li><a href="https://github.com/PostHog/posthog-js/commit/be08a6477588e0201770ef80618a45d5c1398ffa"><code>be08a64</code></a> docs: centralize SDK examples in official docs (<a href="https://redirect.github.com/PostHog/posthog-js/issues/3825">#3825</a>)</li>
<li><a href="https://github.com/PostHog/posthog-js/commit/1a2ddb73f693f27fd454063ac115f674325c4d89"><code>1a2ddb7</code></a> chore: update versions and lockfile [version bump]</li>
<li>Additional commits viewable in <a href="https://github.com/PostHog/posthog-js/compare/posthog-js@1.352.0...posthog-js@1.386.8">compare view</a></li>
</ul>
</details>
<br />
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/hamilton/network/alerts).
</details>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@hamilton.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Bump @opentelemetry/core and posthog-js in /ui/frontend [hamilton]
Posted by "jernejfrank (via GitHub)" <gi...@apache.org>.
jernejfrank merged PR #1636:
URL: https://github.com/apache/hamilton/pull/1636
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@hamilton.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org