Navigate

Versioning and the fb tag

Pyric has its own semver. Firebase compatibility is a separate claim, made by an npm dist-tag:

npm install pyric@fb12.13

fb<major>.<minor> points at the newest pyric release whose conformance gates passed against that line of Firebase. It means “conformance-tested against Firebase 12.13” — not “equal to” and not “full parity.” The tag is a statement about what was tested, not about how much matched.

Three rules govern it:

  • It is machine-issued. The tag moves only when the release script runs compat:check against the pinned Firebase version and it comes back green. Nobody moves it by hand because they believe pyric is ready.
  • It tracks major.minor lines, never patches. There is no fb12.19.1. Old fb tags are never deleted or moved backward, so an install pinned to an older line stays reproducible.
  • It links to numbers, not a slogan. The claim behind the tag is inspectable on the conformance scoreboard: public runtime surface, public type surface, and fidelity of tracked behavior, per service. “Tested against” is a link, never a vibe.

The same tested-against version appears everywhere a user forms an impression: the README badge, the npm description, pyric --version, and the docs header.

Today: pyric’s pinned conformance version is 12.19.0, and the newest fb tag is fb12.13, which points at alpha.24. An exp publish moves no fb tag, so fb12.19 appears only when a latest or next publish passes compat:check against that pin. Until then, npm install pyric@fb12.19 fails, and npm install pyric@exp gets the release tested against 12.19. A fb tag can point at an alpha release — compatibility and stability are separate claims, and alpha, latest, and fb12.19 can all resolve to the same publish, each making its own.

Bumping the pinned Firebase version re-snapshots the upstream surface; the diff is the worklist, and the new line’s tag appears only when compat:check passes against the new pin.

Firestore query-proof limits

List authorization uses a conservative proof engine. It supports document-independent rules, scalar equality and finite in constraints, positive membership guaranteed by array-contains, and sufficient positive OR branches through helper expansion. Query-pinned scalar fields may also determine authorization lookup paths. Every finite alternative must pass the residual auth, lookup, and query-limit checks (at most 30 combinations). Unpinned data, dynamic per-document membership sets, candidate identities, and unbounded range proofs remain documented limitations (firestore#24c). These local tests do not establish hosted Firebase parity for an application ruleset.

An unsupported query still returns permission-denied. Pyric adds a queryProof diagnostic to request events and the error’s denialContext (also available in modular FirebaseError.customData). It distinguishes unsupported-predicate, unsupported-path, constraints-not-satisfied, residual-denied, and no-rule. Proof failures identify the authored rule separately from any residual expression that actually evaluated false. Captures and Studio preserve this distinction; older captures may lack it.

Query identity retains non-equality filters such as in separately from the proof projection. Operand identities may be bounded digests or opaque references; diagnostic collection does not inspect arbitrary application objects. Neither a local proof limitation nor successful local tests establish a production observation for an unverified query/rules combination.