Skip to content
Lint & Type Check

fix(plugin-security): the app default permission set resolves from the first level that NAMES one (#15298) #30326

Sign in to view logs

fix(plugin-security): the app default permission set resolves from the first level that NAMES one (#15298)

fix(plugin-security): the app default permission set resolves from the first level that NAMES one (#15298) #30326

Triggered via pull request September 4, 2026 11:34
@hotlonghotlong
synchronize #15311
claude/issue-15298-declared-permission-sets-docblock
Status Success
Total duration 18m 23s
Artifacts –

lint.yml

on: pull_request
Type Check · source gates
2m 38s
Type Check · source gates
Type Check · workspace
10m 11s
Type Check · workspace
Type Check · debt ledger
4m 0s
Type Check · debt ledger
Type Check · consumer gates
4m 39s
Type Check · consumer gates
Lint & Repo Gates
18m 19s
Lint & Repo Gates
TypeScript Type Check
5s
TypeScript Type Check
Fit to window
Zoom out
Zoom in

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.