Skip to content

chore: bump @formo/analytics to 1.42.1 - #358

Merged
yosriady merged 1 commit into
mainfrom
chore/bump-formo-analytics-1.42.1
Oct 9, 2026
Merged

yosriady merged 1 commit into
mainfrom
chore/bump-formo-analytics-1.42.1

Conversation

@yosriady

@yosriady yosriady commented Oct 9, 2026 •

Copy link
Copy Markdown
Contributor

Bumps every example to @formo/analytics@^1.42.1.

1.42.1 fixes EIP-1193 mode: a chainChanged from a wallet that is not the active one no longer clears the active wallet's address, so track() keeps it (getformo/sdk#412). Wagmi mode is not affected.

Lockfiles

Lockfiles change only the @formo/analytics entries (specifier, version, integrity, snapshot keys), the same shape as #355: 38 files, 114+/114-. Five lockfiles (with-dynamic, with-farcaster, with-next-page-router, with-porto, with-tempo) re-resolved unrelated packages under --lockfile-only, so their SDK entries were edited by hand instead. All 19 pass pnpm install --frozen-lockfile --lockfile-only, and with-react and with-next-page-router install with --frozen-lockfile.

e2e

Mirrors the SDK's new twowallets scenario (getformo/sdk#412): the active wallet answers eip6963:requestProvider like a real extension, another wallet changes network, and track() must keep the active address. runTwoWallets and the scenario are now identical to the SDK's test/e2e copy.

Local run against the published 1.42.1: node behaviours.mjs → all 36 scenarios passed (wagmi rows included).

🤖 Generated with Claude Code


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

View guided diff Turn on auto-fix

@yosriady
yosriady marked this pull request as ready for review October 9, 2026 11:25
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@cubic-dev-ai cubic-dev-ai Bot left a comment •

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

All reported issues were addressed across 40 files

Reply with feedback, questions, or to request a fix.

View guided diff | Turn on auto-fix | Re-trigger cubic

Comment thread e2e/scenarios.mjs
@socket-security

socket-security Bot commented Oct 9, 2026 •

Copy link
Copy Markdown

Dependency limit exceeded — report not shown.

This pull request scan exceeded the 10,000-dependency limit applied to this scan, so the results are incomplete and may be inaccurate. To avoid reporting false positives, Socket has not posted a report.

Upgrade your plan to raise the dependency limit and get complete reports, or view the partial scan in the dashboard.

Socket is always free for open source. If this is a non-commercial open source project, contact us to request a free Team account.

Bumps every example to @formo/analytics@^1.42.1. 1.42.1 fixes EIP-1193
mode: a chainChanged from a wallet that is not the active one no longer
clears the active wallet's address (getformo/sdk#412). Wagmi mode is not
affected.

Lockfiles change only the @formo/analytics entries. Five of them
(with-dynamic, with-farcaster, with-next-page-router, with-porto,
with-tempo) re-resolved unrelated packages under --lockfile-only, so their
SDK entries were edited by hand instead; all 19 pass
`pnpm install --frozen-lockfile --lockfile-only`.

e2e: mirror the SDK's new twowallets scenario (answersRequests, trackAfter)
so the sweep checks the fix against the published package.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@yosriady
yosriady force-pushed the chore/bump-formo-analytics-1.42.1 branch from d8eb809 to 4ce8d37 Compare October 9, 2026 12:13
@yosriady
yosriady merged commit 7a085fd into main Oct 9, 2026
44 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant