-
Notifications
You must be signed in to change notification settings - Fork 55
chore: merge node v5 to main #470
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.
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
Conversation
Size Change: -884 B (-0.37%) Total Size: 238 kB
ℹ️ View Unchanged
|
@@ -4,6 +4,7 @@ on: | |||
push: | |||
branches: | |||
- main | |||
- v5 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
rollback once its done
@rafaeelaudibert if you up to merge main into this branch and fix the conflicts, we can then do a final review/test together and release all 3 major versions o/ |
@hpouillot adding you as a reviewer here because you've done a ton of work on the Node SDK recently too and might have some thoughts about things worth including in a new version |
@marandaneto workin on it now |
Node 20+ is the latest maintained version, so let's move to it. We're forced to use it on posthog-ai anyways because of the `@google/ai` package so let's standardize it across all libraries. We're also running CI on Node 20 already.
Ok, I dont think my merge went well 😮💨. Will retry it again. I'm seeing a lot of failures for no reason |
Cherry-picking proved to be easier than merging/rebasing, so here's my new PR: #522 Trying to get CI green in there 🧑🏭 |
Superseded by #522 |
Problem
new major for RN, Node and Web
All PRs merged into this branch have already been reviewed.
See the changelog of each package to see whats removed/renamed/changed, etc
Changes
Release info Sub-libraries affected
Bump level
Libraries affected
Changelog notes