chore(deps)(deps): bump actions/cache from 4 to 5#5
Merged
Conversation
Bumps [actions/cache](https://github.com/actions/cache) from 4 to 5. - [Release notes](https://github.com/actions/cache/releases) - [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md) - [Commits](actions/cache@v4...v5) --- updated-dependencies: - dependency-name: actions/cache dependency-version: '5' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
This was referenced May 4, 2026
Merged
jkeeley2073
added a commit
that referenced
this pull request
May 10, 2026
…ransparency surface (#171) Closes the 1 🔴 finding from `docs/PHASE5-DRIFT-AUDIT.md` § 2 by adding the chrome footer that was missing from Wave 1. Coverage-statement copy is locked from `docs/ui/screens/empty-landing.md` § Section 4 and now renders on every screen — not just the empty-landing surface — per the answer-with-citations § Screen zones #5 spec. This is the third (final) PR in the Phase 5 Wave 1 drift-audit fix roadmap. PR-T1 (#166) shipped token alignment; PR-F-chrome-nav-rework (#169) simplifies the header to a single "What we cover" link and relocates Status to the footer added here. Changes: - BrandFooter.razor (NEW) — chrome surface in Components/Layout/. MudBlazor-strict (MudText + MudLink + native <footer> landmark only). Renders the locked coverage statement, the "What we cover →" link to /about styled with Color.Success (= --accent-grounded #34d96a per the PR-T1 spec alignment), the project name, the canonical GitHub link (Target=_blank + rel="noopener noreferrer" tabnabbing protection), and the Status link relocated from the prior 4-link header. - MainLayout.razor — mounts <BrandFooter /> inside <MudLayout> after </MudMainContent>. Two-line edit. - BrandFooterTests.cs (NEW) — 5 bUnit tests pin the footer landmark + aria-label, the locked coverage-statement copy, the "What we cover" link target + label, the GitHub link's tabnabbing-safe attributes, and the relocated Status link. - MainLayoutTests.cs — extended with a drift guard that asserts BrandFooter mounts in the rendered tree (catches a future MainLayout edit silently dropping the footer). The coverage-statement test is the load-bearing one — without it, the next "let's tighten the footer copy" edit can quietly drop the "first-party data on 8 active manufacturers" line that establishes the project's coverage-transparency posture (ADR-0027 § 4). Sequencing note: this branch was forked off origin/main *before* PR #169 (chrome-nav-rework) merges, so the file-disjoint Status link appears in BOTH the existing BrandHeader.razor (header) and the new BrandFooter.razor (footer) until #169 lands. Merge order should be #169 first, then this PR — at which point Status appears once, in the footer, per ADR-0027 § 1. Tests: 55 → 61 passing in Web.Tests (+5 BrandFooterTests + 1 MainLayoutTests drift-guard). Solution build clean (0 warnings / 0 errors). Local review: 0 actionable 🔴 (the 1 🔴 flagged about MudLink silently dropping rel was a false alarm — the bUnit test mechanically verifies rel="noopener noreferrer" reaches the rendered <a>, and that test passed; MudLink supports attribute splatting in this version. The other 🔴 about Status duplication is the merge-order note above, not a code-change concern). 1⚠️ (file-header comment was too long; tightened in this PR — kept the spec authority + ADR citations only, dropped the rationale prose). Mechanical 10-item self-audit: 0 🔴 / 0⚠️ / 5 ✅ / 5 N/A.
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/cache from 4 to 5.
Release notes
Sourced from actions/cache's releases.
... (truncated)
Changelog
Sourced from actions/cache's changelog.
... (truncated)
Commits
27d5ce7Merge pull request #1747 from actions/yacaovsnc/update-dependencyf280785licensed changes619aeb1npm run build generated dist filesbcf16c2Update ts-http-runtime to 0.3.56682284Merge pull request #1738 from actions/prepare-v5.0.4e340396Update RELEASES8a67110Add licenses1865903Update dependencies & patch security vulnerabilities5656298Merge pull request #1722 from RyPeck/patch-14e380d1Fix cache key in examples.md for bun.lockDependabot 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)