fix(deps): update production dependency minor updates

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@opencoredev/email-sdk (source)	^0.5.0 → ^0.6.1
flags (source)	^4.0.6 → ^4.1.0

---

Release Notes

opencoredev/email-sdk (@​opencoredev/email-sdk)

v0.6.1

Compare Source

Patch Changes

• c80935f: Add the Convex Email component package with durable queued sends, retries, fallback adapters, idempotency, webhook ingestion, and test-mode delivery controls.

  Ship the component alongside a patch SDK release so the docs, package entrypoints, and provider surface move forward as 0.6.1 instead of a larger version jump.

v0.6.0

Compare Source

Minor Changes

• 4db1cd7: Add an official Iterable adapter for target campaign email sends.
• 2b1fbf1: Add the Sequenzy transactional email adapter, CLI support, docs, tests, and a local API-auth smoke check.

vercel/flags (flags)

v4.1.0

Compare Source

Minor Changes

• #​385 201f9d5 Thanks @​dferber90! - When applications call evaluate() or precompute() function from flags/next it now defers bulk evaluation to the underlying adapters in case those support it, or otherwise falls back to evaluating each flag individually.

  This speeds up evaluation for applications that need to evaluate multiple flags at once, as the runtime needs to handle fewer promises and more work is reused. In testing we have seen a 20x improvement when called with 100 flags.

  import { evaluate } from "flags/next";
  import { flagA, flagB } from "../flags";
  
  // pass a list of flags
  const [valueA, valueB] = await evaluate([flagA, flagB]);
  
  // pass an object
  const { a, b } = await evaluate({ a: flagA, b: flagB });

  Adapters can opt into bulk evaluation by implementing a bulkDecide method and setting a stable adapterId. When both are present, flag evaluation groups flags that share the same adapterId and identify source and invokes bulkDecide once per group instead of calling decide per flag. Flags without a bulk-capable adapter still resolve through the normal per-flag path inside evaluate() and still benefit from now reusing the shared per-request headers, cookies, and overrides reads.

  Tracing reflects this grouping. evaluate() (and therefore precompute()) now emits an evaluate span carrying a flagCount attribute. Within it, bulk-evaluated flags no longer emit an individual per-flag run span; instead each adapter group emits a single batch span (carrying the adapterId, the keys evaluated in the batch, and cachedCount/overrideCount/decidedCount attributes summarizing how the batch resolved) so per-flag instrumentation overhead is not reintroduced. Flags that fall back to the per-flag path continue to emit their own flag span as before.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "after 9am every weekday,before 5am every weekday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
vazen-web	Ready	Preview, Comment	Jun 10, 2026 11:20am

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
vazen-docs	Skipped		Jun 10, 2026 11:20am