Skip to content

chore(deps): update dependency posthog-js to v1.304.0 #999

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
renovate merged 1 commit into from
Dec 11, 2025
Merged

chore(deps): update dependency posthog-js to v1.304.0 #999

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions bun.lock
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@
"lucide-react": "0.556.0",
"mermaid": "11.12.2",
"next": "16.0.8",
"posthog-js": "1.302.2",
"posthog-js": "1.304.0",
Copy link
Copy Markdown

@sentry sentry Bot Dec 11, 2025

Choose a reason for hiding this comment

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

Bug: The update to posthog-js specifies version 1.304.0, which does not appear to be published on npm. This will likely cause the build to fail.
Severity: CRITICAL | Confidence: High

🔍 Detailed Analysis

The package.json file is being updated to use version 1.304.0 of posthog-js. However, an investigation indicates that this version does not appear to be publicly available on the npm registry, with the latest published version being 1.303.1. This discrepancy will likely cause dependency resolution to fail during the build process, preventing the application from being built or deployed. While the update also includes changes to rrweb and adds a product tours feature, these are secondary as the primary issue is the potential non-existence of the specified package version.

💡 Suggested Fix

Verify if posthog-js version 1.304.0 is available in a private registry or if it is an unpublished version. If it is not available, the dependency should be pinned to the latest stable and published version, such as 1.303.1, until 1.304.0 is officially released and confirmed to be stable.

🤖 Prompt for AI Agent 
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: package.json#L44

Potential issue: The `package.json` file is being updated to use version `1.304.0` of
`posthog-js`. However, an investigation indicates that this version does not appear to
be publicly available on the npm registry, with the latest published version being
`1.303.1`. This discrepancy will likely cause dependency resolution to fail during the
build process, preventing the application from being built or deployed. While the update
also includes changes to `rrweb` and adds a product tours feature, these are secondary
as the primary issue is the potential non-existence of the specified package version.

Did we get this right? 👍 / 👎 to inform future reviews.
Reference ID: 6985875

"react": "19.2.1",
"react-dom": "19.2.1",
"react-medium-image-zoom": "5.4.0",
Expand Down
Loading