docs(web): note the v3.5.1.0 patch on the What's New card - #86
Merged
Conversation
The hero read v3.5.1.0 while the newest release card still ended at v3.5.0.0. Follows the existing convention for patch releases: a "patched through" suffix on the meta line plus a "Patched in" paragraph, as v3.3.0.x and v3.4.0.1 both carry. Describes the change in visitor terms, since the fixes are to this page itself: the notch-safe gutter, the 44px touch minimum, and overflow being prevented rather than hidden. No VERSION bump — v3.5.1.0 is already released and this only corrects its release note. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
savvides
added a commit
that referenced
this pull request
Aug 30, 2026
…#87) * fix(ci): move linter workflow into .github so GitHub actually runs it The linter workflow landed at `github/workflows/linter.yml` — no leading dot — which created a stray top-level `github/` directory alongside the real `.github/`. GitHub only reads workflows from `.github/workflows/`, so the workflow never ran. Its job is named `run-lint`, which is the context the "Protect Main Branch" ruleset requires. With the file unreachable, that required check could never report and every pull request sat at BLOCKED indefinitely — the entire #72-#86 backlog had to be merged with admin bypass. Moving the file to `.github/workflows/linter.yml` lets the job run and lets the required check resolve on its own. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * fix(ci): pin super-linter to the validators this repo can actually pass Moving the workflow into .github/ made run-lint report for the first time — and it failed immediately, on a pull request whose only change was the rename itself. Super-linter runs every validator it can detect unless at least one VALIDATE_* is set to true. Three of those defaults are wrong here: - JSCPD uses a 0% duplicate threshold and found 9.53% across 41 clones. Most of those are the .cjs/.js module twins (canvas-crawler, parser-helper, dossier-compiler, evidence-base, prompts, renderer-helper) that CLAUDE.md mandates so the modules stay both node-testable and browser-loadable. The validator flags the architecture as a defect. - CHECKOV failed CKV2_GHA_1 on linter.yml and test.yml for not declaring top-level permissions. - YAML_PRETTIER failed on linter.yml's own formatting. Naming a validator switches super-linter to opt-in, so this pins the set to the three that pass on this repo and are worth gating on: actionlint (the class of bug that caused this), gitleaks (the extension handles API keys), and yamllint. Bash is deliberately excluded. shellcheck reports 52 findings across the 29 shell files — 4 errors, 5 warnings, 43 notes, 14 of them SC2086. That is worth fixing, but as its own change, not as a gate that blocks every pull request from day one. Also adds the least-privilege permissions block, which resolves the "Failed to call GitHub Status API: 403" errors in the run log, and cleans up the formatting yamllint warned about. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
The hero reads v3.5.1.0 but the newest release card still ended at v3.5.0.0.
Adds the
· patched through v3.5.1.0suffix and aPatched in v3.5.1.0paragraph, matching how v3.3.0.x and v3.4.0.1 are presented on the same page. Written in visitor terms because the fixes are to this page itself: the notch-safe gutter, the 44px touch minimum, and overflow prevented rather than hidden.No VERSION bump — v3.5.1.0 is already released; this corrects its release note.
Verified: smoke-test 362/362, both landing suites pass (including the rendered one that now guards this file), doc checkers clean.