Release status
Stable package availability, validation, and adoption boundaries.
Organization package
The npm package is @clipin/convex-teams. Its first stable version, 1.0.0, is published under latest. The GitHub repository remains clipinfit/convex-teams.
The earlier unscoped name claim and release candidate were removed from npm. Install @clipin/convex-teams.
Verified in development
The component and host suite covers ownership, role preservation, invitation acceptance, recipient checks, delivery failures, bounded lists, deletion, and preference repair.
Actual local Convex transactions also verify the final-seat race, concurrent personal bootstrap, and duplicate membership grants.
The invite pagination fix is published as convex-invite@0.1.1. Teams uses that version without a local patch. A clean packed npm consumer passes against registry dependencies, including a local backend check of pagination and acceptance rollback.
Membership grants now use an atomic stored count. Legacy counts initialize in bounded batches. Slug allocation has a fixed attempt budget. Runtime tests cover both paths, including the final-seat race and very large seat policies on a local backend.
Release validation
The published candidate passed clean registry installation checks on Convex 1.43.0 and 1.45.0 and both consumer rehearsals. Those checks used the earlier unscoped candidate. The scoped archive also passed both consumer rehearsals and native installation checks on Convex 1.43.0 and 1.45.0. The exact stable registry package passed the native installation check, and its integrity matches the tested archive. Both consumers also passed against the exact stable registry package. The unscoped artifacts are removed.
Production inventory, both consumer rehearsals, recovery, attribution, and supported-version checks are recorded in the release audit. Feedtwin production cutover is a separate operation.
Track the completion PRD and the invite pagination fix.
Version policy
Unfinished component releases use the alpha tag. The first stable target is 1.0.0. After 1.0, incompatible API or documented authorization changes require a major version. Compatible additions use a minor version; compatible fixes use a patch.
Checkpoint commits do not change the package version. Each published artifact has a new immutable version. The release procedure is in RELEASING.md.