chore: bump @elizaos/plugin-n8n-workflow to 1.2.2

[standujar]

Summary

• Bumps @elizaos/plugin-n8n-workflow from 1.2.1 to 1.2.2

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
eliza-cloud-v2	Building	Preview, Comment	Feb 19, 2026 1:49pm

[claude]

PR Review: chore: bump @elizaos/plugin-n8n-workflow to 1.2.2

Summary: Simple patch-level dependency bump with no logic changes. Low risk.

---

Code Quality & Correctness

The changes are minimal and correct:

• package.json: version pin updated from 1.2.1 → 1.2.2
• bun.lock: package hash updated and "configVersion": 0 added

The configVersion: 0 field in bun.lock is a new lockfile format field introduced by a newer version of Bun — this is expected and harmless, just a side effect of regenerating the lockfile.

---

Potential Concern: Peer Dependency Mismatch

The updated plugin declares an exact peer dependency:

"peerDependencies": { "@elizaos/core": "1.7.2" }

However, this project uses:

"@elizaos/core": "1.7.3-alpha.2"

This is a peer version mismatch. Bun typically doesn't hard-fail on peer dependency mismatches (unlike npm with --legacy-peer-deps), so it likely won't break anything at install time. But it's worth flagging: if the plugin relies on @elizaos/core@1.7.2-specific APIs or types, there could be runtime or type-level incompatibilities with 1.7.3-alpha.2.

Recommendation: Confirm with the plugin maintainer that 1.2.2 is compatible with @elizaos/core@1.7.3-alpha.2, or check whether the peer dep should be a range (e.g., >=1.7.2) rather than a hard pin.

---

Security

No security concerns. This is a lockfile-verified bump with a new content hash (sha512-FA5U...), so the resolved package is tamper-verified.

---

Test Coverage

No tests are expected or needed for a version bump of this kind.

---

Overall: Looks fine to merge pending confirmation that the peer dependency mismatch is benign. The Vercel preview build will validate runtime behavior.