Repository navigation
chore(ci)(deps): bump actions/stale from 9.0.0 to 10.1.1 - #21
Merged
Merged
Conversation
Bumps [actions/stale](https://github.com/actions/stale) from 9.0.0 to 10.1.1. - [Release notes](https://github.com/actions/stale/releases) - [Changelog](https://github.com/actions/stale/blob/main/CHANGELOG.md) - [Commits](actions/stale@v9.0.0...v10.1.1) --- updated-dependencies: - dependency-name: actions/stale dependency-version: 10.1.1 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
dependabot
Bot
deleted the
dependabot/github_actions/actions/stale-10.1.1
branch
February 1, 2026 02:48
This was referenced May 25, 2026
Closed
This was referenced Aug 31, 2026
This was referenced Sep 1, 2026
This was referenced Sep 4, 2026
This was referenced Sep 4, 2026
This was referenced Sep 10, 2026
akarma-synetal
pushed a commit
to akarma-synetal/framework
that referenced
this pull request
Sep 17, 2026
…_CONTEXTS row (objectstack-ai#17803) Closes objectstack-ai#15233 Clause-②: no Implements the director ruling on objectstack-ai#15233 (summon objectstack-ai#21, comment 5615315987) as written: the seventh `REQUIRED_CONTEXTS` row, plus the platform-readings count line six to seven. ⛔ **GOVERNED SURFACE — do not arm, do not enqueue.** This diff touches `.claude/skills/pm-dispatch/references/platform-readings.md`, so per `AGENTS.md` Post-Task Checklist item 2 it is pushed, opened, and left **awaiting a human merge**. Auto-merge was **not** armed and will not be. `Governed Surface Queue Guard` demanding an authorized approver on this PR is the guard working, not a failure. --- ## 1. The row (acceptance 1) `scripts/check-required-contexts.mjs`, all four fields as the ruling names them: workflow `governed-surface-guard.yml` (the registry spells the basename; `scanWorkflows` joins it under `.github/workflows/`), job id `governed-surface-guard`, context `Governed Surface Queue Guard`, `authorized` citing objectstack-ai#12427's 2026-08-27 confirmation (closed `completed` 2026-08-27T07:51Z, comment 5436049459). ## 2. The re-check, both readings (acceptance 2) `NODE_OPTIONS=--use-env-proxy node scripts/check-required-contexts.mjs --verify-required-set`, exit 0 both times. **BEFORE** (at `952b9c5e59`): ``` required-set sweep: 7 live required context(s) on main, 0 registered-but-not-required, 1 required-but-unpinned. ⛔ direction B — required in the live set, pinned by NO registry row (1). • Governed Surface Queue Guard — from main (active) ``` **AFTER** (this branch): ``` required-set sweep: 7 live required context(s) on main, 0 registered-but-not-required, 0 required-but-unpinned. ✅ the live required set and this registry agree in both directions. ``` ⇒ **1 → 0**, against an unchanged live set of 7. The contrasting 1 is what shows the row did the work. ## 3. The count line, hand-followed (acceptance 3) `platform-readings.md` now reads 七个 and names the seventh. Hand-followed, exactly as triage 5586769327 warned: the ledger is an `INSTRUCTION_SURFACES` entry whose `mustName` **does not require exclusivity**, so the *scan* half would have stayed green on a stale count line forever.⚠️ **One half of that warning is falsified, and it is worth recording.** The scan does not red — but `--self-test` **does**: ``` • the readings ledger is a scanned surface naming all 7 required contexts — got {"file":".claude/...platform-readings.md","mustName":[ ...six... ]} ``` That assertion derives the expected length from `REQUIRED_CONTEXTS.length`, so the ledger's `mustName` array **is** machine-coupled to the registry. The *prose count line* is the part nothing reads. So: the count line was hand-followed (it had to be), and `mustName` gained the seventh name (the gate demanded it). ## 4. Reverse-read — including the zeros (acceptance 4) Scanned every surface that states the required set, for `six` / 六个: | surface | reading | | :--- | :--- | | `.claude/.../review-checklist.md` | **0** — states only the two it names; no count | | `.claude/.../pm-dispatch/SKILL.md` | **0** | | `docs/launch-readiness.md` | **0** | | `CLAUDE.md` | **0** | | `docs/releases-maintenance.md` | 1 hit, **not this** ("at most six hours") | | `.claude/.../spec-property-retirement/SKILL.md` | 1 hit, **not this** (第六个 variant-docs) | | tree-wide `six` outside these | ~30 hits, **all unrelated** (query keys, API primitives, error rows) | | **`AGENTS.md:505-510`** | ⛔ **STILL SIX — and out of this PR's scope** | `AGENTS.md` states *"six contexts block"* and *"A check outside those six is advisory and rides through."* With the guard live-required, that sentence is **false**, and its failure mode is objectstack-ai#12427's incident shape: a seat reads it, treats the guard as advisory, and arms. `AGENTS.md` is explicitly off-limits for this card, and `mustName` does not red on it either (same non-exclusivity). ⇒ Filed as **objectstack-ai#17798**, unassigned and ungraded. --- ## ⛔ 5. One residual, NOT fixed here — `check:required-contexts` is RED on this branch Adding the row makes the registry judge the workflow that publishes the context, and that is where the row earns its keep. `--self-test` has **6 failures, all one root cause**: ``` • the checked-in workflows pass the pin — got [".github/workflows/governed-surface-guard.yml's `pull_request:` trigger carries `branches:`. A base-filtered trigger does not run at all on a PR whose base branch is outside the filter, so it publishes NO check run there — not a skip, an absence — and every required context in this file sits permanently pending on every PR based on a feature branch (objectstack-ai#16482 …)"] ``` This is a **pre-existing live defect**, not one this PR introduces: the guard has been required since 2026-08-27 while carrying `branches: [main]`, the exact base-filter shape objectstack-ai#16482 removed from `ci.yml` and `lint.yml` after measuring six card PRs showing **zero** of the required contexts. The registry had simply never been allowed to look. The remedy is mechanical and the repo has already ruled its shape — the self-test's own standing assertion is *"the checked-in workflows carry NO base filter on pull_request — the required contexts report for any base (objectstack-ai#16482)"*, and both sibling workflows carry a ⭐-comment saying so. Removing `branches: [main]` from the guard's `pull_request:` leg turns all 6 green. Note it **widens** coverage (the `pull_request` leg deliberately exits 0; the refusing leg is `merge_group`), so it is not a loosening. ⛔ **I did not make that edit**: this session's safety classifier refuses agent edits to `.github/workflows/**` (`[CI Bypass]`), and no ruling on this card covers a third file. ⇒ **Maintainer's call**, either on this PR or as its own card. ## What was carried with the row - `mustName` gains the seventh name — forced by `--self-test`, see §3. - The self-test's workflow corpus is now **derived from `REQUIRED_CONTEXTS`** instead of a hand-listed `lint.yml`/`ci.yml` pair. Without this, the newly-registered file is never read and `judge` reports *"never read — a scan that reads nothing cannot report a pass (objectstack-ai#4690)"* through **every** fixture, so three fixtures were asserting against the wrong problem list. Enrolling an eighth context can no longer skip this step. ## Gates `--verify-required-set` exit 0 (both readings above) · `check:nul-bytes` 0 · `check:pm-dispatch-gates` 0 · `check:agent-test-spelling` 0 · `check:doc-authoring` 0 · `check:parse-guard` 0 · `check:entry-guard` 0 · `check-self-test-wired` (+`--self-test`) 0 · `check-scripts-symbol-anchors` 0 · `check-declaration-mirrors` 0 · `check-whole-set-label-write` 0 · `check-ci-filter-parity` 0 · `check-closing-keyword-parity` 0 · `check-self-test-workflow-commands` 0 · `check-governed-queue-guard --self-test` 0 · `check-comment-mask-corpus` 0. Derived from `dispatch-gates.mjs --commands --repo objectstack-ai/objectstack` at `952b9c5e59`. ⛔ `check:required-contexts` **RED** — §5, one root cause, deliberate. Re-measured independently (⛔ not taken on report): `check-cross-package-test-inputs.mjs --self-test` is **exit 0 both with and without** `NODE_OPTIONS=--use-env-proxy` (156/156 cases each) — objectstack-ai#15234's landing holds, so the ruling's re-check flag is safe to use. **Changeset: skipped**, measured — repo-root `scripts/` and `.claude/**` are not shipped; no package `files[]` carries either path, and the repo root is `private: true`. Applied as the `skip-changeset` **label**. --- ## 维护者速读(草稿) **改了什么** — 给 CI「必需检查」注册表补上第七行,钉住 `Governed Surface Queue Guard` 这个名字;并把 PM 席位手册里「六个」的计数改成「七个」。两处都只是**记录**,不改任何仓库设置。 **为什么改** — 这个守卫是保护受管面(`.claude/**`、`AGENTS.md`、ADR 等)的那道门,2026-08-27 就已经生效,但注册表一直没写它。后果不是今天失守,而是**哪天有人改了那个 job 的名字,这道门会无声脱落**,而注册表存在的全部意义就是防这一件事。 **风险与代价(含回滚)** — 改动只有记录性的两处加两处配套,风险极低;回滚就是还原这一个 commit,没有数据迁移、没有已发布产物。⚠️ 但补上这一行之后,门禁第一次去看那个工作流,发现它带着一个会让检查在部分 PR 上**根本不报告**的过滤器(详见上面第 5 节)。那一处**本 PR 没有动**,需要您定夺。 **席位意见** — (留空,待席位填写) **你要做的** — ① 决定第 5 节那个 `branches:` 过滤器是就在本 PR 删掉,还是另开一张卡;② 本 PR 属受管面,**需要您手动合并**,不会进合并队列。 --- _Generated by [Claude Code](https://claude.ai/code/session_012GKcPZbMoGq7WPzKLfRBTU)_ --------- Co-authored-by: Claude <noreply@anthropic.com>
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps actions/stale from 9.0.0 to 10.1.1.
Release notes
Sourced from actions/stale's releases.
... (truncated)
Changelog
Sourced from actions/stale's changelog.
Commits
9971854build(deps): bump actions/checkout from 4 to 6 (#1306)5611b9dbuild(deps): bump actions/publish-action from 0.3.0 to 0.4.0 (#1291)fad0de8Improves error handling when rate limiting is disabled on GHES. (#1300)39bea7dAdd Missing Input Reading foronly-issue-types(#1298)e46bbabbuild(deps-dev): bump@types/nodefrom 20.10.3 to 24.2.0 and document breakin...65d1d48build(deps-dev): bump eslint-config-prettier from 8.10.0 to 10.1.8 (#1276)5f858e3Addonly-issue-typesoption to filter issues by type (#1255)3a9db7eUpgrade to node 24 (#1279)8f717f0Bumps form-data (#1277)a92fd57build(deps): bump undici from 5.28.5 to 5.29.0 (#1251)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)