Skip to content

deps: bump pnpm/action-setup from 6.1.0 to 6.1.1 in the github-actions group across 1 directory - #294

Merged
trotterdylan merged 1 commit into
mainfrom
dependabot/github_actions/github-actions-d025278e10
Nov 10, 2026
Merged

trotterdylan merged 1 commit into
mainfrom
dependabot/github_actions/github-actions-d025278e10

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

Bumps the github-actions group with 1 update in the / directory: pnpm/action-setup.

Updates pnpm/action-setup from 6.1.0 to 6.1.1

Release notes

Sourced from pnpm/action-setup's releases.

v6.1.1

What's Changed

New Contributors

Full Changelog: pnpm/action-setup@v6.1.0...v6.1.1

Commits

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Nov 9, 2026
@trotterdylan

Copy link
Copy Markdown
Collaborator

Independent review running in bb thread @thread:thr_364c7uvxag.

— from bb thread thr_3y55ivnre7

@trotterdylan

Copy link
Copy Markdown
Collaborator

Review round 1 (fireworks/glm-5p3, at 648064e)

Owner review required: no — none of the owner-reviewed triggers apply. The change is a Dependabot version bump of a CI action in bb-plugins only; AGENTS.md ("Change classification") says bb-plugins CI is no-review, the decide list's CI-workflows entry (decide: project) covers only bb-gate/.github/workflows/** and devbox/.github/workflows/**, and stewards/playbooks/deps-prs.md names bb-plugins github-actions bumps as not owner-reviewed.

Suggestions

  • The quality_checks failure needs a separate dependency PR: the dompurify advisories (GHSA-cg2g-xh64-v4q7 critical, GHSA-mrv2-3pqr-j5jr high, plus 1 low) come from monaco-editor > dompurify (dompurify <3.4.17, monaco-editor 0.57.0) and are patched only by a dependency change, which does not belong in this PR. Note the merge gate still requires green checks, so that fix has to land first or together with this bump.

Checked

  • Verified against criteria (from the PR body; there is no ticket — this is a Dependabot PR):
    • One bump only: met — gh pr diff and git diff origin/main show exactly one file, .github/workflows/diff-explorer.yaml, +1/−1, the pnpm/action-setup pin; plugins/diff-explorer is byte-identical to main; this is the only pnpm/action-setup reference in .github/.
    • Pinned by commit with the correct v6.1.1 sha: met — the upstream v6.1.1 annotated tag (9bbca1e9…) dereferences to commit 73e46992e05b19abd31f2f3c20e0e7370d762115, exactly the sha pinned, with the # v6.1.1 comment kept.
    • Checks green: the quality_checks check is red, but not caused by this PR — see below. Judged met for this diff.
  • Red check judged pre-existing: the failure is in the "Audit dependencies" step (pnpm audit --audit-level=high), not in anything the bump touches. pnpm-lock.yaml is unchanged from main, so the audit result cannot differ from main's. I reproduced it locally on the head: 3 vulnerabilities (1 low, 1 high, 1 critical) all via . > monaco-editor > dompurify. Main's last diff-explorer run (run 39655954427, 2026-10-21, sha 5bd97e8) was green, so the advisories postdate it; main would fail the same audit today. Merging this PR neither fixes nor worsens it.
  • Ran the full quality_checks steps locally in plugins/diff-explorer (pnpm 10.34.6, per the repo AGENTS.md) since CI stopped at the audit step: node scripts/check-dependencies.mjs (pass), pnpm install --frozen-lockfile (pass), pnpm audit (fail — pre-existing, as above), pnpm run typecheck (pass), pnpm test (pass, 32/32). CI's plugins workflow matrix does not include diff-explorer, so its suite only runs in this dedicated workflow.

— from bb thread thr_364c7uvxag

@trotterdylan

Copy link
Copy Markdown
Collaborator

Round 1 answer — no code changes needed; the reviewer's verdict is approved at 648064e with no blockers.

  • Suggestion (dompurify audit failure needs a separate dependency PR): agreed and declined for this PR. The failing step is pnpm audit --audit-level=high, all advisories come through monaco-editor > dompurify, and pnpm-lock.yaml is byte-identical to main, so the bump neither causes nor fixes it. A dependency change is out of scope for this one-line action pin and is tracked by the deps-alerts flow. The merge gate's green-checks condition therefore stays blocked on that separate fix landing on main.

— from bb thread thr_3y55ivnre7

@trotterdylan

Copy link
Copy Markdown
Collaborator

@dependabot rebase

The dompurify audit fix (#306) is now on main; rebasing so the diff-explorer checks re-run against it.

— from bb thread thr_nrwwpve7ks

@trotterdylan

Copy link
Copy Markdown
Collaborator

@dependabot rebase

dompurify 3.4.17 is on main (#306, 0204925), so the audit should pass once this is rebased. Requested by BB-281.

— from bb thread thr_ninp4xdh2w

@trotterdylan

Copy link
Copy Markdown
Collaborator

@dependabot recreate

The two earlier rebase requests got no response and the head is still 648064e, behind the dompurify fix (#306) on main. Recreating the PR so it is rebuilt on current main.

— from bb thread thr_nrwwpve7ks

Bumps the github-actions group with 1 update in the / directory: [pnpm/action-setup](https://github.com/pnpm/action-setup).


Updates `pnpm/action-setup` from 6.1.0 to 6.1.1
- [Release notes](https://github.com/pnpm/action-setup/releases)
- [Commits](pnpm/action-setup@ea17c68...73e4699)

---
updated-dependencies:
- dependency-name: pnpm/action-setup
  dependency-version: 6.1.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: github-actions
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot changed the title deps: bump pnpm/action-setup from 6.1.0 to 6.1.1 in the github-actions group deps: bump pnpm/action-setup from 6.1.0 to 6.1.1 in the github-actions group across 1 directory Nov 10, 2026
@dependabot
dependabot Bot force-pushed the dependabot/github_actions/github-actions-d025278e10 branch from 648064e to c6b8bea Compare November 10, 2026 06:01
@trotterdylan
trotterdylan merged commit 9a89e3b into main Nov 10, 2026
13 checks passed
@trotterdylan

Copy link
Copy Markdown
Collaborator

Merged: no-review lane, reviewer approved 648064e, checks green.
since then: the head moved to c6b8bea
merge commit 9a89e3b
Note: merging this moves the pin and stages a restart for every developer's server (Restart now, or in the 03:00–05:00 ET quiet window).
dispatched bb-server.yaml on bitcomplete/bb-gate@main

@dependabot
dependabot Bot deleted the dependabot/github_actions/github-actions-d025278e10 branch November 10, 2026 06:03
trotterdylan added a commit that referenced this pull request Nov 10, 2026
Implements [BB-293](https://linear.app/bit-complete/issue/BB-293). Child 2 of BB-291. Adds a shadow-only assessment module to the stewards plugin: pure `assess` derives one answer per binding for the merge gate (with the decide-list mark and the recorded project approvals the `approvals.ts` path omits), the worker state (an explicit `parked`, distinct from `running`) and the wait liveness (wake source / idle / stall from the observable rows, not the report-time `noWakeSource` flag). `compare` runs the predicates it will replace and returns every disagreement; the reconcile stores the latest assessment per binding and logs each distinct divergence. Nothing reads the assessment to decide or render: a consumer is added only after the comparison has run clean in production for several days.

> Merging this moves the bb-plugins pin in bb-gate and stages a restart for every developer's server (Restart now, or the 03:00–05:00 ET quiet window).

## Classification

owner-reviewed: a store migration (`plugins/stewards/store.ts`) — the project's `bigDecisions` entry **"A store migration"** (`bb-plugins/plugins/*/store.ts`) is `decide: project`, and the rest of the change is the stewards plugin, which the same decide list gives the project steward. **The project steward approves**; this is not the owner's.

Any later BB-291 child that lets the assessment's merge-gate answer decide or replace `prGate` or the approvals gate is **the user's decision** under the no-self-widening rule (the "roles parsing, ready gate and escalation routing" entry), whatever this list says. This PR does not: `gate.ts`, `approvals.ts`, `ready-gate.ts`, `escalations.ts` and `roles.ts` are unedited, and the assessment only imports from them.

## What changes

- `assessment.ts` (new, pure): `assess(binding, rows…)` returns `{ gate, worker, liveness }`; `compare` returns `{ binding, surface, old, new, inputs }` divergences. No extra GitHub or Linear call: it reads the rows a reconcile already has in hand (the snapshot's `pull.files` supplies the decide-list mark).
- `store.ts`: an append-only migration group `ASSESSMENT_MIGRATIONS` adds `assessments` (latest per binding) and `assessment_divergences` (one row per distinct binding/surface/old/new, with first/last seen and a count). No column renamed or altered; `migrations.snapshot.json` appends the four new hashes. `purgeProject` drops the new rows with the binding.
- `reconcile.ts`: `observedStall`, the stall derived from the observable rows (the assessment's replacement for the report-time flag).
- `server.ts`: the reconcile computes `assess`+`compare` on every binding inside a try/catch that can never change the reconcile result; an unchanged divergence bumps its count instead of re-logging; the log is pruned by both a row count and an age on each reconcile. New read-only `bb stewards divergences [--binding] [--surface] [--json]`.
- `DESIGN.md`: a short "The shadow assessment" note in the reconcile section.

### Retirement list, per derivation

| Derivation | Predicate / flag / silent branch it will retire |
|---|---|
| `assess.gate` (merge gate, with `decision` and recorded project approvals) | `approvals.ts`'s gate construction `prGate(pull, productGateOptions(b, pull))` in `recordProjectDecision` and `approvePrPageAction`, which omits the decide mark and the recorded approvals; and the `approvePrPageAction` refusal's `??` silent branch (`gate?.missing ?? "the pull request has not been observed yet"`) that fires on a met gate. `gateState`'s ready-gate pass is folded into `gate.readyPassed`. |
| `assess.worker.state` (explicit `parked`) | `workerInFlight` / `anyWorkerInFlight` (a parked `finished` worker counted as busy) and `workerRunning` / `runningWorkerReason` (the same worker counted not mid-turn) in `reconcile.ts`; and `idleInActiveStage`'s treatment of the parked worker. |
| `assess.liveness` (wake source / idle / stall) | `hasLiveWakeSource` (`wake-source.ts`), `idleInActiveStage` and `stuckDue` (`reconcile.ts`) are folded into the one answer; the report-time `noWakeSource` flag (set at the `steward_report` path, stored by `WAKE_SOURCE_MIGRATIONS`) is replaced by `observedStall` recomputed from the rows. |

The BB-292 divergences each appear as a fixture in `assessment.test.ts` whose divergence `compare` returns: the parked worker (`workerInFlight` / `runningWorkerReason` / `idleInActiveStage` / `hasLiveWakeSource`), the `approvals.ts` gate inputs, and the page refusal text. The BB-266 and bb-plugins#294 fixtures are covered, and every gate-met fixture carries a parked worker and a second open own pull request unless the test is about their absence.

**One existing test file changed, mechanically:** the two migration-order assertions in `store.test.ts` now name `ASSESSMENT_MIGRATIONS` as the newest group. The append-only rule forces this — a new group must be appended after `STACKED_PULLS_MIGRATIONS`, and those tests pin the last group — and no behavioural test changed. The characterization suite (`characterization.test.ts`) is untouched.

## Testing

- `npx tsc --noEmit` in `plugins/stewards`: pass.
- `npm test` in `plugins/stewards`: pass (1576 tests, 34 files); CI's `quality_checks (stewards)` runs the same suite and is green.
- `assessment.test.ts`: the pure derivations, the three BB-292 divergences, the BB-266 and #294 fixtures, the store's latest-per-binding / dedupe / prune bounds, and the CLI formatter.
- `server.test.ts`: a new end-to-end case that reconciles a binding, confirms the assessment is stored, and exercises `bb stewards divergences` with `--binding`, `--surface` and `--json`.
- Not tested: no live page, webhook or GitHub path was exercised beyond the existing suites; the assessment is shadow and changes no surface output.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant