chore(release): 1.34.0

[yosriady]

Release PR for 1.34.0, covering the Privy identity clustering work merged in #304.

Changes

File	Change
package.json	1.33.1 → 1.34.0
src/version.ts	1.30.1 → 1.34.0 (regenerated)
.gitignore	ignore .pnpm-store/

src/version.ts had drifted three releases behind. It was still reporting 1.30.1 while the package shipped 1.33.1, because earlier releases did not run the npm version lifecycle that regenerates it. That value is compiled into the bundle and sent with events, so it has been misreporting the SDK version. Regenerated here.

.gitignore now covers .pnpm-store/, the local content-addressable store pnpm creates in the repo root. It was untracked and unignored, so every pnpm version failed with ERR_PNPM_UNCLEAN_WORKING_TREE.

After merging

The release workflow triggers on a v* tag and hard-fails if the tag does not match package.json, so tag only after this lands on main:

git checkout main && git pull
git tag v1.34.0
git push origin v1.34.0

Then verify: npm view @formo/analytics version

What 1.34.0 contains

identify(user) accepts a Privy user directly and identifies every wallet linked to that user's DID, so a multi-wallet Privy user clusters into one Formo user instead of fragmenting into one per address.

Verified end to end against a live Privy app and a real Formo project: one identify per linked wallet sharing the DID and anonymous_id, attribution pinned to the active wallet, and each social link re-emitting exactly one identify per wallet with the socials landing on all addresses in user_profiles_mv.

Release notes

Two behaviour changes affecting all callers, not just Privy:

• Identify dedup is now profile-aware. An identify() whose properties changed re-emits instead of being suppressed for the session. This is what makes account linking propagate. Callers passing a volatile property (a timestamp, a random id) will emit one identify per call rather than one per session. Worth watching identify volume for 24-48h after release.
• An identify on a chain in tracking.excludeChains no longer mutates identity state. Previously it updated currentAddress/currentUserId and wrote the user-id cookie, then dropped the event and left the wallet dedup-marked, so it never re-emitted after switching to an allowed chain.

Verification

749 tests passing; lint, tsc, and full build clean. package.json and src/version.ts agree, which is what the workflow checks.

🤖 Generated with Claude Code

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}