Skip to content

Conversation

@robbie-c
Copy link
Member

@robbie-c robbie-c commented Dec 8, 2025

Changes

Let's bump all our deps, starting with react dev deps, as this involves a couple of other fixes to tests.

Note: Bundled size will probably fail as it doesn't pnpm install between versions

Release info Sub-libraries affected

Libraries affected

  • All of them
  • posthog-js (web)
  • posthog-js-lite (web lite)
  • posthog-node
  • posthog-react-native
  • @posthog/react
  • @posthog/ai
  • @posthog/nextjs-config
  • @posthog/nuxt
  • @posthog/rollup-plugin
  • @posthog/webpack-plugin

Checklist

  • Tests for new code
  • Accounted for the impact of any changes across different platforms
  • Accounted for backwards compatibility of any changes (no breaking changes!)
  • Took care not to unnecessarily increase the bundle size

If releasing new changes

  • Ran pnpm changeset to generate a changeset file
  • Added the "release" label to the PR to indicate we're publishing new versions for the affected packages

@vercel
Copy link

vercel bot commented Dec 8, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Updated (UTC)
posthog-js Ready Ready Preview Dec 8, 2025 1:03pm
posthog-nextjs-config Ready Ready Preview Dec 8, 2025 1:03pm

@github-actions
Copy link
Contributor

github-actions bot commented Dec 8, 2025

📝 No Changeset Found

This PR doesn't include a changeset. A changeset (and the release label) is required to release a new version.

How to add a changeset

Run this command and follow the prompts:

pnpm changeset

Remember: Never use major version bumps for posthog-js as it's autoloaded by clients.

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

Additional Comments (1)

  1. packages/react/package.json, line 32-34 (link)

    logic: peerDependencies are too permissive for React 19 upgrade

    With React 19 and @types/react 19 in catalog, users with React 16-18 will face peer dependency conflicts. The peerDependencies should require >=19.0.0 to match the new dev dependencies.

7 files reviewed, 1 comment

Edit Code Review Agent Settings | Greptile

@github-actions
Copy link
Contributor

github-actions bot commented Dec 8, 2025

"target": "ES2018"
"target": "ES2018",
"paths": {
"react": ["./node_modules/@types/react"],
Copy link
Contributor

Choose a reason for hiding this comment

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

Is it needed ? Typescript cannot pick it up automatically ?

@robbie-c robbie-c merged commit ab42a12 into main Dec 8, 2025
39 of 40 checks passed
@robbie-c robbie-c deleted the feat/bump-react-package-and-move-more-things-to-catalog branch December 8, 2025 14:00
"target": "ES2018"
"target": "ES2018",
"paths": {
"react": ["./node_modules/@types/react"],
Copy link
Member Author

Choose a reason for hiding this comment

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

This fixed some bleed of react types elsewhere in the monorepo (react@19) into the react-native package(react@18)

@@ -1,5 +1,5 @@
import * as React from 'react'
import { renderHook } from '@testing-library/react-hooks'
Copy link
Member Author

Choose a reason for hiding this comment

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

this has moved

@robbie-c robbie-c mentioned this pull request Dec 8, 2025
17 tasks
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.

3 participants