Skip to main content

RFC — Confirm stable @mekari/pixel3 version with the Pixel3 team

Bucket item: A11 · Class: 🟡 Standard · Jira Story: pending mint (Task: TF-3555) · Epic: TF-3500

Source: Qontak_Stack_Analysis_Repository_Detail_July_2026, qontak-customer-fe tab, row 21.

Context / Problem​

@mekari/pixel3 is pinned in package.json to 1.0.10-dev.0 — an exact pin (no caret) on a prerelease version. Support status is Unknown internally; there's no confirmed stable line to track, which means every future bump is a guess rather than a decision.

Proposed change​

Coordinate with the Pixel3 team to confirm whether a stable (non--dev) release exists or is planned that qontak-customer-fe should move to, and get a recommended version/upgrade path.

Execution plan (call to action)​

  1. Reach out to the Pixel3 team (Slack/ticket) with the current pin (1.0.10-dev.0) and ask for their recommended stable line.
  2. Record their guidance here (or in a linked follow-up) — either a target stable version, or an explicit "stay on this dev pin until X" note.
  3. If a stable version exists, file a follow-up Task to bump package.json to it (separate from this confirmation-only item).

Risks & rollback​

  • Risk: none — this item is a coordination/confirmation step, no code change.
  • Rollback: n/a.

Open questions​

  1. Does the Pixel3 team have a stable release already, or is one planned this quarter?
  2. If none exists yet, what's an acceptable interim pin policy (e.g. ~1.0.10-dev.0 vs exact)?