Skip to content

feat(spec,auth)!: one declared audience posture for self-registration — invite_only|email_domain|open, default invite_only #24913

feat(spec,auth)!: one declared audience posture for self-registration — invite_only|email_domain|open, default invite_only

feat(spec,auth)!: one declared audience posture for self-registration — invite_only|email_domain|open, default invite_only #24913

Triggered via pull request August 25, 2026 02:42
Status Success
Total duration 11m 3s
Artifacts –

lint.yml

on: pull_request
Type Check · source gates
2m 26s
Type Check · source gates
Type Check · workspace
10m 26s
Type Check · workspace
Type Check · debt ledger
10m 34s
Type Check · debt ledger
Type Check · consumer gates
7m 14s
Type Check · consumer gates
Lint & Repo Gates
9m 12s
Lint & Repo Gates
TypeScript Type Check
2s
TypeScript Type Check
Fit to window
Zoom out
Zoom in

Annotations

1 error and 2 warnings
Lint & Repo Gates
` in it is labelled a window rather than an anchor. And a `fix`
Release section coverage
content/docs/releases/index.mdx: the v17 entry's status reads "current series: 17.1.0, released 2026-08-20", but the newest released 17.x version is 17.2.0. The sibling gate only rejects a PRE-RELEASE here, so a superseded STABLE version passes it — "(current series: 17.0.0)" while 17.2.0 is on `latest` is the exact state that shipped. Name the newest release.
Release section coverage
content/docs/releases/v17.mdx: @objectstack/spec 17.2.0 is published (it has a `## 17.2.0` section in packages/spec/CHANGELOG.md) but NO heading on this page names the 17.2 series. Fold it in under a running section — the shape both current pages use is "# What's new in 17.2.0" plus "### 17.2.0" in the upgrade checklist. This gate writes no prose and cannot: a curated section is a judgement about what is user-facing, read out of the per-package changelogs. It only reports that the section is absent.