chore(deps-dev): bump tailwindcss from 4.3.1 to 4.3.2 - #310
Closed
dependabot[bot] wants to merge 2 commits into
Closed
chore(deps-dev): bump tailwindcss from 4.3.1 to 4.3.2#310dependabot[bot] wants to merge 2 commits into
dependabot[bot] wants to merge 2 commits into
Conversation
Bumps [tailwindcss](https://github.com/tailwindlabs/tailwindcss/tree/HEAD/packages/tailwindcss) 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) --- updated-dependencies: - dependency-name: tailwindcss dependency-version: 4.3.2 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
# Conflicts: # package-lock.json # package.json
ContributorAuthor
Looks like tailwindcss is up-to-date now, so this is no longer needed. |
BigSimmo added a commit
that referenced
this pull request
Aug 12, 2026
…310) and the ledger loss-detector (#311) (#1870) * docs(issues): capture the fuzzy-search drug-match finding and the loss-detector #310 — PR #1851's fuzzy catalogue search matches DIFFERENT drugs at edit distance 2. Measured by running the PR's own algorithm rather than reading it: fluoxetine -> duloxetine (Damerau counts the lu->ul transposition as one edit, both are 10 chars, so the >=8 tier's 2-edit budget allows it) and prednisone -> prednisolone. Intended recovery still works (sertraline, olanzapine) and the short-term guards hold (SSRI/SNRI, ADHD/ODD). Two real mitigations recorded so it is not over-read: fuzzy fires only when nothing matched literally, and sub-5-character terms are excluded. Tested fix is one line — cap the >=8 tier at 1 edit, which kills both cross-drug hits and keeps every legitimate typo case. Blast radius is eleven modules including medications.ts, because catalog-search.ts feeds the whole clinical catalogue. #311 — promote the derived ledger loss-detector into scripts/. Two main-merges silently reverted ledger edits this session, including the whole #293 refutation, and the hand-enumerated recovery list could not catch it. The derived version has now earned its place twice. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017paT42ZVMf8jaLtkjFxdy5 * chore(ledger): record the finding-capture handoff Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * chore(ci): run focused PR 1870 ledger correction * chore(ci): use repository Node version for PR 1870 fix * ci(pr-1870): merge current main and finalise ledger fixes * ci(pr-1870): scope final verification and publish normally --------- Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
BigSimmo pushed a commit
that referenced
this pull request
Aug 13, 2026
Pins ledger #310: with both the exact drug and its two-edit neighbour in the catalogue, fluoxetine must not surface duloxetine and prednisone must not surface prednisolone, while single-edit typo recovery (setraline->sertraline) keeps working. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WBdo125Dh3idPcF7CmCCmG
BigSimmo pushed a commit
that referenced
this pull request
Aug 13, 2026
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WBdo125Dh3idPcF7CmCCmG
BigSimmo pushed a commit
that referenced
this pull request
Aug 13, 2026
Four merge-safe intake requests, no canonical ledger edit: - P1 rec: no gate detects a merged PR whose content is silently reverted by a later merge resolution. Blob sweep over origin/main found seven such PRs since 2026-08-06, six first wiped at one commit in the PR #1815 unblock chain. The reverts took each PR's tests in the same stroke, which is why nothing went red. - P2 task: re-land PR #1800 (fuzzy catalogue search) with the #310 one-edit cap applied in the same commit. - P2 task: re-land PR #1803 (--shadow-tight retirement); 67 files on main still reference the retired alias. - update #310: re-scoped. The defect is not reachable on main because the matcher is absent, not because it was fixed, so the row must not be closed and the fix belongs in the #1800 re-land. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DuYJz8hauCsCdx8r4fXiZU
BigSimmo added a commit
that referenced
this pull request
Aug 13, 2026
…earch (#1851) * fix: restore overwritten search features * fix(search): address ticker and fuzzy ranking review * test(search): run submitted-root ticker regression in critical CI * test(search): require fuzzy field reason signals * fix(search): expose fuzzy field match reasons * fix(ci): register submitted-root regression in UI shards * fix(search): bound long-token typo recovery to one edit * test(search): prevent cross-drug fuzzy matches * Add wrong-drug exclusion regression test for the fuzzy typo cap Pins ledger #310: with both the exact drug and its two-edit neighbour in the catalogue, fluoxetine must not surface duloxetine and prednisone must not surface prednisolone, while single-edit typo recovery (setraline->sertraline) keeps working. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WBdo125Dh3idPcF7CmCCmG * style(tests): format merged navigation assertions --------- Co-authored-by: Claude <noreply@anthropic.com>
BigSimmo added a commit
that referenced
this pull request
Aug 13, 2026
BigSimmo added a commit
that referenced
this pull request
Aug 14, 2026
…main (#1943) * docs(issues): close#310 — fuzzy catalogue cap already landed on main The #310 re-land task was overtaken by 247a359 ("Add tappable phone suggestion ticker and conservative fuzzy catalog search (#1851)", 2026-08-14 02:03 +0800), which put the Damerau-Levenshtein catalogue matcher back on main already carrying the one-edit cap and both regression tests. No source change is needed; src/lib/catalog-search.ts is untouched by this commit. The pending inbox requests for #310 had inverted against that reality. Request e1506952 ("closeable when #1851 merges") was cancelled by 31650c87 at 05:48 on 2026-08-14 — after the merge at 02:03 — leaving 8621298b ("NOT REACHABLE ON MAIN ... do not close this row") as the sole surviving mutation. Because ledger-inbox mutationConflicts only throws when two or more mutations for one id survive cancellation, the next reconcile would have applied that stale text quietly, stamping "the matcher is gone, do not close" onto a row whose code is present, capped and tested. Queued through the tool, never hand-written: - cancel 8621298b, whose stop-rule against closing #310 was conditioned on the code being absent from main - done #310, carrying the evidence: typoDistanceLimit is >= 5 -> 1 with no >= 8 two-edit tier, both test files, 19/19 passing, and a re-run of the original measurement method (hazard pairs 0, intended recovery 1, all five guards 0, co-present ranking clean) docs/outstanding-issues.md is deliberately untouched — reconcile owns it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0122UC4BL5R39kz41WbBYcPj * fix(issues): drop stale fuzzy-search cancellation --------- Co-authored-by: Claude <noreply@anthropic.com>
BigSimmo pushed a commit
that referenced
this pull request
Aug 14, 2026
Runs `npm run issues:reconcile` from a fresh base off origin/main (0011a05), applying all 35 pending requests with 5 cancellation decisions. The motivating case is #310, which main was carrying with a false statement. Request 8621298b ("NOT REACHABLE ON MAIN ... The whole matcher is gone") had been applied, while the cancellation queued against it was lost in the PR #1943 squash. The correcting closure 00428ff0 survived as a pending request, so this reconcile applies it: #310 now records that 247a359 re-landed the matcher with typoDistanceLimit >=5 -> 1 and both regression tests, and the false text is gone from the file. The lost cancellation was deliberately NOT re-filed. Its target is already in applied/, so planRequestBatch would reject it with "cancel request targets missing pending request" and block every future reconcile. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0122UC4BL5R39kz41WbBYcPj
BigSimmo added a commit
that referenced
this pull request
Aug 14, 2026
docs(issues): reconcile the inbox batch, correcting a false #310 row on main
4 tasks
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 from 4.3.1 to 4.3.2.
Release notes
Sourced from tailwindcss's releases.
Changelog
Sourced from tailwindcss's changelog.
Commits
056a1554.3.2 (#20281)c8b081dAdd suggestions for named opacity modifiers (#20287)c46f654Ensure--alpha(…)is seen as acolor, and--spacing(…)is seen as a `le...5e9f66eEnsure@variantcan be used in JS based APIs (#20252)707c23bEnsure custom variants can be used via@variantinaddBase(#20247)127d170Add bare value support forauto-rows-*andauto-cols-*(#20229)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)