feat(metadata,objectql): a leaf /view-container subpath keeps objectql lean under ADR-0076 - no manager, chokidar, glob or js-yaml in the core closure
#30357
Triggered via pull request
September 4, 2026 12:34
Status
Success
Total duration
18m 15s
Artifacts
–
lint.yml
on: pull_request
Type Check · source gates
2m 39s
Type Check · workspace
9m 44s
Type Check · debt ledger
5m 35s
Type Check · consumer gates
7m 6s
Lint & Repo Gates
18m 11s
TypeScript Type Check
4s
Annotations
2 warnings
|
Release section coverage
content/docs/releases/index.mdx: the v17 entry's status reads "current series: 17.2.0, released 2026-08-23", but the newest released 17.x version is 17.3.0. The sibling gate only rejects a PRE-RELEASE here, so a superseded STABLE version passes it — "(current series: 17.0.0)" while 17.3.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.3.0 is published (it has a `## 17.3.0` section in packages/spec/CHANGELOG.md) but NO heading on this page names the 17.3 series. Fold it in under a running section — the shape both current pages use is "# What's new in 17.3.0" plus "### 17.3.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.
|