Skip to content

chore(deps): bump posthog-node from 5.61.1 to 5.63.1 - #993

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/bun/posthog-node-5.63.1
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/bun/posthog-node-5.63.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

Bumps posthog-node from 5.61.1 to 5.63.1.

Release notes

Sourced from posthog-node's releases.

posthog-node@5.63.1

5.63.1

Patch Changes

  • #5545 28fe8c0 Thanks @​onmax! - Parse Node stack frames for functions named async without a leading parenthesis in the filename. (2026-11-06)
  • Updated dependencies [28fe8c0]:
    • @​posthog/core@​1.64.1

posthog-node@5.63.0

5.63.0

Minor Changes

  • #5580 aa66d4c Thanks @​haacked! - metrics.histogram() accepts a bounds option that sets the histogram's bucket boundaries, and beforeSend sees and can change them. The first sample of a histogram (name and unit) fixes its bounds until the client resets. A later sample with different bounds is recorded in the fixed buckets and logs a warning, and a sample with invalid bounds is dropped. The experimental posthog.flags.request.duration histogram now uses the bounds [50, 75, 100, 150, 200, 300, 400, 500, 750, 1000, 1500, 2000, 3000, 5000, 10000] ms, so its p50 and p95 resolve between 50ms and 5s. This changes the metric's buckets, which its experimental status allows. (2026-11-05)

Patch Changes

  • Updated dependencies [aa66d4c]:
    • @​posthog/core@​1.64.0

posthog-node@5.62.0

5.62.0

Minor Changes

  • #5509 71c2464 Thanks @​Silthus! - posthog.emails.send() can now send email content your code rendered, such as HTML from React Email. Give the email a templateKey and a subject, and pass html, text or both.

    const posthog = new PostHog("phc_...", { secretKey: "phs_..." });
    const { data, error } = await posthog.emails.send({
    to: "user@example.com",
    distinctId: "user_123",
    templateKey: "password-reset",
    subject: "Reset your password",
    html: renderedHtml,
    });
    if (error) throw error;
    // 'delivered', 'bounced', ...
    const { data: status } = await posthog.emails.get(data.id);

    You need a project secret API key, the kind that starts with phs_. Create one under Project secret API keys in your project settings. Set its Transactional email scope to Write to send emails, or to Read for a key that only reads statuses. Pass it to the client as secretKey. Set appHost to your PostHog app URL when you self-host PostHog or send through a reverse proxy.

    PostHog records each email's delivery, opens and clicks on the person with that distinctId. It groups every email with the same templateKey, so you see their metrics and logs in one place. The SDK retries a request that hits a network error, a rate limit or an outage twice by default. Every send carries an idempotency key, so a retry never sends the email twice. Pass your own idempotencyKey, such as welcome:user_123, and your job runner's retries are safe too.

... (truncated)

Changelog

Sourced from posthog-node's changelog.

5.63.1

Patch Changes

  • #5545 28fe8c0 Thanks @​onmax! - Parse Node stack frames for functions named async without a leading parenthesis in the filename. (2026-11-06)
  • Updated dependencies [28fe8c0]:
    • @​posthog/core@​1.64.1

5.63.0

Minor Changes

  • #5580 aa66d4c Thanks @​haacked! - metrics.histogram() accepts a bounds option that sets the histogram's bucket boundaries, and beforeSend sees and can change them. The first sample of a histogram (name and unit) fixes its bounds until the client resets. A later sample with different bounds is recorded in the fixed buckets and logs a warning, and a sample with invalid bounds is dropped. The experimental posthog.flags.request.duration histogram now uses the bounds [50, 75, 100, 150, 200, 300, 400, 500, 750, 1000, 1500, 2000, 3000, 5000, 10000] ms, so its p50 and p95 resolve between 50ms and 5s. This changes the metric's buckets, which its experimental status allows. (2026-11-05)

Patch Changes

  • Updated dependencies [aa66d4c]:
    • @​posthog/core@​1.64.0

5.62.0

Minor Changes

  • #5509 71c2464 Thanks @​Silthus! - posthog.emails.send() can now send email content your code rendered, such as HTML from React Email. Give the email a templateKey and a subject, and pass html, text or both.

    const posthog = new PostHog("phc_...", { secretKey: "phs_..." });
    const { data, error } = await posthog.emails.send({
    to: "user@example.com",
    distinctId: "user_123",
    templateKey: "password-reset",
    subject: "Reset your password",
    html: renderedHtml,
    });
    if (error) throw error;
    // 'delivered', 'bounced', ...
    const { data: status } = await posthog.emails.get(data.id);

    You need a project secret API key, the kind that starts with phs_. Create one under Project secret API keys in your project settings. Set its Transactional email scope to Write to send emails, or to Read for a key that only reads statuses. Pass it to the client as secretKey. Set appHost to your PostHog app URL when you self-host PostHog or send through a reverse proxy.

    PostHog records each email's delivery, opens and clicks on the person with that distinctId. It groups every email with the same templateKey, so you see their metrics and logs in one place. The SDK retries a request that hits a network error, a rate limit or an outage twice by default. Every send carries an idempotency key, so a retry never sends the email twice. Pass your own idempotencyKey, such as welcome:user_123, and your job runner's retries are safe too.

    A send with your own content also takes from, replyTo and captureEngagement: false. Set migratedFrom on the client to tell PostHog which email provider you moved from. A failed call returns an EmailError with PostHog's code and the HTTP statusCode.

    Docs: Send transactional emails with Node.js and the transactional email overview. (2026-11-05)

... (truncated)

Commits
  • d2d8a26 chore: update versions and lockfile [version bump]
  • 9644778 chore: update versions and lockfile [version bump]
  • aa66d4c feat(metrics): give posthog.flags.request.duration finer buckets (#5580)
  • 5663aff chore: update versions and lockfile [version bump]
  • 71c2464 feat(node): send email content from code with emails.send (#5509)
  • 25e06dc chore: update versions and lockfile [version bump]
  • 88744a9 fix(node): skip local evaluation warnings for client-only flags (#5532)
  • 0d8f89d ci(node): integrate shared benchmark reports (#5454)
  • 03ca515 ci(node): add paired SDK performance benchmarks (#5453)
  • 48f16d8 chore: update versions and lockfile [version bump]
  • Additional commits viewable in compare view

Dependabot compatibility score

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 commands and options

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)

Bumps [posthog-node](https://github.com/PostHog/posthog-js/tree/HEAD/packages/node) from 5.61.1 to 5.63.1.
- [Release notes](https://github.com/PostHog/posthog-js/releases)
- [Changelog](https://github.com/PostHog/posthog-js/blob/main/packages/node/CHANGELOG.md)
- [Commits](https://github.com/PostHog/posthog-js/commits/posthog-node@5.63.1/packages/node)

---
updated-dependencies:
- dependency-name: posthog-node
  dependency-version: 5.63.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Nov 9, 2026
@coderabbitai

coderabbitai Bot commented Nov 9, 2026

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 9d91825e-d42f-4dbf-a8a9-b219e3d3d6af

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addednpm/​posthog-node@​5.63.18710089100100

View full report

@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

Thanks @dependabot[bot] for keeping our dependencies current! 🙌

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Automated approval for Dependabot dependency update.

@hermes-exosphere

hermes-exosphere commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

pr-autopilot finished looking at the failing CI on commit 4186a6d. What it found is in the comment here.

@hermes-exosphere

Copy link
Copy Markdown
Contributor

CI is failing: OSV-Scanner (commit 4186a6d). The update does not seem to be the cause, so nothing was pushed. A person needs to look at this.

Why it failed
OSV-Scanner reports GHSA-3jp2-3mrg-2vxc (High) in oauthlib 4.0.0, locked in sdk/python/uv.lock; fixed version is 4.0.1. This lockfile is unchanged by the PostHog update. Fetched origin/main equals the PR's merge base, fa9307f, and fails identically, so rebasing would not resolve it.

What it ran

  • Docker unavailable; used the official OSV-Scanner v2.5.0 binary matching the CI action image.
  • Ran on PR HEAD: osv-scanner --config=osv-scanner.toml --lockfile=bun.lock --lockfile=Cargo.lock --lockfile=fp-cloud-cli/uv.lock --lockfile=sdk/python/uv.lock --lockfile=sdk/typescript/package-lock.json; exit 1 with the reported oauthlib vulnerability.
  • Ran identical arguments against files extracted from the merge base, also fetched origin/main; exit 1 with the same vulnerability.
  • git status --porcelain and git diff checks confirmed no repository changes.

Diagnosed by gpt-6.1-sol.

pr-autopilot · Codex in a locked-down container · traced by failproofai

@NiveditJain

Copy link
Copy Markdown
Member

Closing: this update was merged to main as part of #999 (601ade2), which rolled every open Dependabot update into one branch.

@dependabot @github

dependabot Bot commented on behalf of github Nov 13, 2026

Copy link
Copy Markdown
Contributor Author

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot
dependabot Bot deleted the dependabot/bun/posthog-node-5.63.1 branch November 13, 2026 07:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

autopilot:needs-human dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants