Repository navigation
fix(deps): bump @posthog/warlock to 0.2.3 - #827
Merged
Merged
Conversation
0.2.3 ships warlock #59: the PII capture-rule bleed fix (a propless capture() no longer false-positives a following identify()) and remediation text naming the $set / $set_once / setPersonProperties escape hatches. #804 migrated pi onto warlock but stayed on 0.2.2, so main currently runs the pi fence on the un-fixed rules; this closes that. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
🧙 Wizard CIRun the Wizard CI and test your changes against wizard-workbench example apps by replying with a GitHub comment using one of the following commands: Test all apps:
Test all apps in a directory:
Test an individual app:
Show more apps
Results will be posted here when complete. |
Collaborator
Author
|
/wizard-ci basic-integration/next-js |
🧙 Wizard CI ResultsTrigger ID:
Configuration
|
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.
Problem
oopsie
#804 migrated the pi harness onto
@posthog/warlockbut left the pin at0.2.2. Warlock #59 (the PII capture-rule fixes) shipped as 0.2.3, so main currently runs the pi security fence on the un-fixed rules:0.2.2's PII rule uses an argument gap that doesn't stop at), so a properties-lessposthog.capture('event')bleeds into a followingposthog.identify(userId, { email })and false-flags it. This is the exact "identify() triggering the PII rule" symptom the incident was about.0.2.3fixes it ([^{]*→[^{)]*).0.2.2's block message says "use posthog.identify() or person properties";0.2.3names the concrete escape hatches (identify(),setPersonProperties(),$set/$set_once), which the pi fence surfaces to a blocked agent so it can self-correct.Changes
@posthog/warlock0.2.2→0.2.3(exact pin, as before) + lockfile.Test plan
pnpm installresolves0.2.3; lockfile diff is the warlock entry only, no dependency drift.0.2.3API (no API changes, rules-only release).yara-hooks+ pisecuritysuites green (62 tests).🤖 Generated with Claude Code