chore(deps): bump the production-minor-patch group with 4 updates

[dependabot]

Bumps the production-minor-patch group with 4 updates: posthog-node, @anthropic-ai/claude-agent-sdk, @anthropic-ai/sdk and @clerk/nextjs.

Updates posthog-node from 5.40.0 to 5.41.0

Release notes

Sourced from posthog-node's releases.

posthog-node@5.41.0

5.41.0

Minor Changes

• #4105 203284a Thanks @​eli-r-ph! - Add opt-in Capture V1 support. Set the POSTHOG_CAPTURE_MODE=v1 environment variable to submit analytics events to the Capture V1 endpoint (/i/v1/analytics/events) instead of the legacy /batch/ endpoint, on both the batched and immediate send paths. The default remains v0, so existing behavior is unchanged unless you opt in. Opt-in is env-var-only during the transition (no public option), so nothing on the API surface has to be removed when v1 later becomes the default.

  Capture V1 uses Bearer auth, lifts legacy $-sentinel properties into a typed options object, and does per-event partial retry with exponential backoff clamped against Retry-After. Dropped and undelivered events are surfaced on the client error channel as a CaptureV1Error. $ai_* events continue to use the legacy submitter for now, regardless of the capture mode.

  In v1 mode, $ai_* events are routed to an isolated in-memory queue and flushed independently of the Capture V1 queue, so the two transports never share a batch and a failure on one cannot re-send events already accepted on the other. Each queue keeps its own retry/durability semantics: the legacy queue re-queues on network failure (retrying on later flushes), while the V1 queue exhausts the sender's own attempt budget per cycle and then surfaces the failure rather than re-queuing. (2026-07-11)

Patch Changes

• Updated dependencies [203284a]:
  • @​posthog/core@​1.40.2

Changelog

Sourced from posthog-node's changelog.

5.41.0

Minor Changes

• #4105 203284a Thanks @​eli-r-ph! - Add opt-in Capture V1 support. Set the POSTHOG_CAPTURE_MODE=v1 environment variable to submit analytics events to the Capture V1 endpoint (/i/v1/analytics/events) instead of the legacy /batch/ endpoint, on both the batched and immediate send paths. The default remains v0, so existing behavior is unchanged unless you opt in. Opt-in is env-var-only during the transition (no public option), so nothing on the API surface has to be removed when v1 later becomes the default.

  Capture V1 uses Bearer auth, lifts legacy $-sentinel properties into a typed options object, and does per-event partial retry with exponential backoff clamped against Retry-After. Dropped and undelivered events are surfaced on the client error channel as a CaptureV1Error. $ai_* events continue to use the legacy submitter for now, regardless of the capture mode.

  In v1 mode, $ai_* events are routed to an isolated in-memory queue and flushed independently of the Capture V1 queue, so the two transports never share a batch and a failure on one cannot re-send events already accepted on the other. Each queue keeps its own retry/durability semantics: the legacy queue re-queues on network failure (retrying on later flushes), while the V1 queue exhausts the sender's own attempt budget per cycle and then surfaces the failure rather than re-queuing. (2026-07-11)

Patch Changes

• Updated dependencies [203284a]:
  • @​posthog/core@​1.40.2

Commits

• d7f7c8e chore: update versions and lockfile [version bump]
• 203284a refactor(core): extract sendBatch seam for capture pluggability (#4105)
• d0e531a fix(core): coalesce concurrent flushes (#4120)
• See full diff in compare view

Updates @anthropic-ai/claude-agent-sdk from 0.3.206 to 0.3.207

Release notes

Sourced from @​anthropic-ai/claude-agent-sdk's releases.

v0.3.207

What's changed

• Fixed canUseTool returning {behavior: 'allow'} without updatedInput being rejected as a deny with a raw ZodError message; the tool now runs with the original input per the documented contract
• The Agent tool's structured result now has a published SDK type (AgentToolCompletedOutput) that matches the emitted object exactly

Update

npm install @anthropic-ai/claude-agent-sdk@0.3.207
# or
yarn add @anthropic-ai/claude-agent-sdk@0.3.207
# or
pnpm add @anthropic-ai/claude-agent-sdk@0.3.207
# or
bun add @anthropic-ai/claude-agent-sdk@0.3.207

Changelog

Sourced from @​anthropic-ai/claude-agent-sdk's changelog.

0.3.207

• Fixed canUseTool returning {behavior: 'allow'} without updatedInput being rejected as a deny with a raw ZodError message; the tool now runs with the original input per the documented contract
• The Agent tool's structured result now has a published SDK type (AgentToolCompletedOutput) that matches the emitted object exactly

Commits

• 79b6350 chore: Update CHANGELOG.md
• See full diff in compare view

Updates @anthropic-ai/sdk from 0.110.0 to 0.111.0

Release notes

Sourced from @​anthropic-ai/sdk's releases.

sdk: v0.111.0

0.111.0 (2026-07-10)

Full Changelog: sdk-v0.110.0...sdk-v0.111.0

Features

• api: add support for dreaming (77b28a6)
• tools: gate session tool calls on evaluated_permission; bound idle by server stop_reason (68a6d7b)

Chores

• docs: small updates to field descriptions (e25b885)
• docs: update model example (a33f3f0)
• docs: updates to descriptions and examples (eac4bac)

Changelog

Sourced from @​anthropic-ai/sdk's changelog.

0.111.0 (2026-07-10)

Full Changelog: sdk-v0.110.0...sdk-v0.111.0

Features

• api: add support for dreaming (77b28a6)
• tools: gate session tool calls on evaluated_permission; bound idle by server stop_reason (68a6d7b)

Chores

• docs: small updates to field descriptions (e25b885)
• docs: update model example (a33f3f0)
• docs: updates to descriptions and examples (eac4bac)

Commits

• 9e46760 chore: release main
• 8d461ea feat(api): add support for dreaming
• 9436e29 codegen metadata
• 0aec1e7 feat(tools): gate session tool calls on evaluated_permission; bound idle by s...
• ac2fc67 chore(docs): update model example
• c8af65d chore(docs): updates to descriptions and examples
• 2a3a904 codegen metadata
• 57c56c9 chore(docs): small updates to field descriptions
• See full diff in compare view

Updates @clerk/nextjs from 7.5.16 to 7.5.17

Release notes

Sourced from @​clerk/nextjs's releases.

@​clerk/nextjs@​7.5.17

Patch Changes

• Updated dependencies [1a19409]:
  • @​clerk/backend@​3.11.4

Changelog

Sourced from @​clerk/nextjs's changelog.

7.5.17

Patch Changes

• Updated dependencies [1a19409]:
  • @​clerk/backend@​3.11.4

Commits

• b51e224 ci(repo): Version packages (#9129)
• See full diff in compare view

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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Labels

The following labels could not be found: supply-chain. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 91d148b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR