chore(deps): update dependency posthog-node to v5.35.0#506
Open
renovate[bot] wants to merge 1 commit into
Open
chore(deps): update dependency posthog-node to v5.35.0#506renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
renovate
Bot
force-pushed
the
renovate/posthog-node-5.x-lockfile
branch
from
578067f to
86a4fbc
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
5.34.8→5.35.0Release Notes
PostHog/posthog-js (posthog-node)
v5.35.0Compare Source
Minor Changes
18ea8b5Thanks @dustinbyrne! - Promote feature flag definition cache provider types to the mainposthog-nodeexport and deprecateposthog-node/experimentalimports.(2026-05-21)
Patch Changes
v5.34.10Compare Source
Patch Changes
f42f371Thanks @dmarticus! - Reject semver values with leading zeros in local flag evaluation. Per semver 2.0.0 §2, numeric identifiers must not include leading zeros — values like1.07.3are not valid semver and should not match targeting conditions. Both override values and flag values are now validated; invalid inputs surface asInconclusiveMatchErrorso the condition does not match.(2026-05-21)
v5.34.9Compare Source
Patch Changes
Configuration
📅 Schedule: (in timezone America/New_York)
* 0-23 * * *)🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.