chore(deps-dev): bump @tailwindcss/postcss from 4.3.1 to 4.3.2 - #313
Merged
Merged
Conversation
Bumps [@tailwindcss/postcss](https://github.com/tailwindlabs/tailwindcss/tree/HEAD/packages/@tailwindcss-postcss) from 4.3.1 to 4.3.2. - [Release notes](https://github.com/tailwindlabs/tailwindcss/releases) - [Changelog](https://github.com/tailwindlabs/tailwindcss/blob/main/CHANGELOG.md) - [Commits](https://github.com/tailwindlabs/tailwindcss/commits/v4.3.2/packages/@tailwindcss-postcss) --- updated-dependencies: - dependency-name: "@tailwindcss/postcss" dependency-version: 4.3.2 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Uh oh!
There was an error while loading. Please reload this page.
dependabotBot
deleted the
dependabot/npm_and_yarn/tailwindcss/postcss-4.3.2
branch
July 6, 2026 07:43
BigSimmo added a commit
that referenced
this pull request
Aug 13, 2026
… queue text (#1890) * docs(issues): retire 22 non-actionable ledger rows and correct the #231 queue text A yield review of all 114 open rows against current main. The queue had become roughly 60 tasks and 50 notes; this removes the notes and fixes two places where the ledger was actively misdirecting. The correction that matters most: the recommended-queue entry for #231, the top clinical P1, told every session to "measure and fix the fast-route budget / generation timeout" — an approach #231's own detail records as tested and rejected, because the decisive 40-second probe completed generation in 25.272s with route_deadline_exceeded=false and still failed quality. The session-start hook prints the queue, not the row, so the refuted text was the text agents read. Closed 22 rows: - #304 was already done on main (commit d182844 refreshed the ranking snapshot; generatedAt is 0 days old, not 2026-07-20), yet sat in the queue advertising a freshness fuse that is not armed. - #241#244#272#294#300#257 were standing cautions whose own text says "no action". Each one's knowledge now lives in the code it protects, so closing the row loses nothing. - #196-#200 are five steps of the disaster-recovery checklist that is canonical in docs/operator-backlog.md, with no trigger until a restore. - #86#188 were index rows over children that are individually findable. - #250#253#254 were superseded; #250 and #253 say so themselves. - #156#301#152#236#260 merged into #168, #292 and #169 respectively — each pair or group was one problem recorded two to four times. Demoted 20 rows with a stated reason (premature ops for a single-user prototype, upstream-blocked, measurement-gated, or design-system adoption competing with an open clinical P1). The Pri cell is unchanged because the writer has no --pri flag — which is now #313. Added three rows for mechanism gaps this sweep exposed: rows outliving their own completion (#312), the missing --pri flag (#313), and the queue being able to contradict the row it cites with no guard (#314). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DuYJz8hauCsCdx8r4fXiZU * docs(ledger): record the ledger yield review handoff Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DuYJz8hauCsCdx8r4fXiZU * Keep recovery work visible and pin forced colors --------- Co-authored-by: Claude <noreply@anthropic.com>
BigSimmo pushed a commit
that referenced
this pull request
Aug 13, 2026
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DuYJz8hauCsCdx8r4fXiZU
BigSimmo pushed a commit
that referenced
this pull request
Aug 13, 2026
… writer (#313) Re-prioritising is the mutation triage performs most often, and it was the one mutation the ledger tooling could not express. AGENTS.md and the ledger both require mutating rows only through the writer — precisely because hand-authored rows produced the width, escaping and wrong-table failures the writer exists to stop — so every demotion had to take the forbidden path. npm run issues:update -- '#151' --pri P3 The gap turned out to be three layers deep, and each one looked fine while the others were broken: 1. scripts/outstanding-issues.mjs — updateIssue's editable map had no `pri` entry, so the Pri cell was unreachable. 2. scripts/ledger-inbox.mjs createRequest — the update payload was built from summary/detail/source only, so even once updateIssue accepted pri, the CLI could not emit it. 3. scripts/ledger-inbox.mjs validateRequest — required one of summary/detail/source, so a pri-only request was rejected before it reached either of the above. A re-prioritisation with no prose change is a legitimate triage edit and now counts on its own. Values are validated against the same P1/P2/P3 set `add` uses, at both the request boundary and the writer, and rejected before the guarded write so a bad value reports itself rather than surfacing as a gate refusal about a malformed row. Deliberately per-row: no bulk re-prioritise mode, because a sweep that moves many rows at once should be visible row by row in review. Every assertion here was mutation-tested rather than merely observed passing. Removing `pri` from the editable map makes the writer throw on a pri-only request; dropping the createRequest passthrough makes the CLI reject it; dropping it from the validator fails the inbox self-test. The writer's own self-test additionally pins that ONLY the Pri cell moves — an off-by-one there would write a priority over the ID or Type cell and still produce a structurally valid row. Verified end to end through the real CLI: `issues:update '#90' --pri P3` queues a valid merge-safe request. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DuYJz8hauCsCdx8r4fXiZU
BigSimmo pushed a commit
that referenced
this pull request
Aug 14, 2026
Queues six immutable inbox requests for the work in this PR. Ordinary branches never edit the canonical ledger, so these reconcile after it lands. - done #313: the dirty-tree refusal shipped. Records the two traps only running it surfaced (the trimmed porcelain that silently disabled the guard, and guard-push's explicit --head), and notes the row's related outstanding-issues.mjs vs issues:done confusion is NOT addressed. - update #211: the plan exists, the migration does not, so the row stays open and stays deprioritised. Carries the 2026-08-12 deprioritisation conclusion forward and corrects the count it rested on — 1,445 across 269 files, not 1,266. - cancel 0e47904b: superseded by that update, which is a strict superset of it. Two pending updates on one row force a cancellation decision at reconcile regardless, so this makes the decision explicit rather than leaving it for whoever reconciles. - update #168 and #258: design and gap documentation landed; neither row is closed, because neither asked only for a document. #258's update records that its cheapest-first option is currently unavailable — checked against all three manifests, not assumed. - add: one new P2 recommendation. Two merge-loss detectors now exist and measure different things — this PR's catches a landing whose content was reverted, PR #1937's concerns a file that never landed at all — and neither covers the other's case. Also carries the undecided scheduling question this PR deliberately left open. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Chrn9bTYFFYzrLZqtpVptW
BigSimmo pushed a commit
that referenced
this pull request
Aug 14, 2026
Applies the pending inbox to docs/outstanding-issues.md as one serial transaction from a fresh origin/main base (0011a05), which is the only path allowed to edit the canonical ledger. 35 requests: 17 done, 7 add, 6 update, 5 cancel. Every request moves verbatim to docs/outstanding-issues-inbox/applied/ as its immutable audit record. One row carried competing mutations — #213, two done requests — resolved by the cancel already queued against one of them. Ledger goes from 328 to 334 rows, 115 open to 99. Includes the five requests queued by PR #1944 but left pending when it merged: closes#313 (the write-discipline dirty-tree refusal shipped), carries #211 forward with its re-measured 1,445 errors while keeping the 2026-08-12 deprioritisation judgment, records the documented state of #168 and #258, and opens #335 for the gap between the two merge-loss detectors. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Chrn9bTYFFYzrLZqtpVptW
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 freeto 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 @tailwindcss/postcss from 4.3.1 to 4.3.2.
Release notes
Sourced from @tailwindcss/postcss's releases.
Changelog
Sourced from @tailwindcss/postcss's changelog.
Commits
056a1554.3.2 (#20281)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 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)