chore(deps): bump actions/checkout from 4 to 6#3
Merged
Conversation
Bumps [actions/checkout](https://github.com/actions/checkout) from 4 to 6. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@v4...v6) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
FarmLox
added a commit
that referenced
this pull request
May 5, 2026
…checkout-6 chore(deps): bump actions/checkout from 4 to 6
FarmLox
added a commit
that referenced
this pull request
May 11, 2026
Closes the wontfix sentinel from the r4 review (ux-findings.md #1 and #3). The Check-for-updates button has been silent during its ~8-second in-flight wait since v1.5.0 and the r3 cooldown extended that silence by another 5 seconds; users on the failure path saw a dim button with no explanation and read it as broken. Screen- reader users got nothing at all. Two new resx strings: UpdateCheck.Status.Checking = "Checking..." UpdateCheck.Status.JustChecked = "Just checked." New TextBlock next to the Check-for-updates button in About, muted body type, AutomationProperties.LiveSetting=Polite so Narrator / NVDA / JAWS announce the transitions. State transitions in AboutWindow.xaml.cs CheckNowClick: click -> "Checking..." result dialog -> (unchanged; user reads MessageBox) dialog dismiss -> "Just checked." cooldown end -> "" OperationCanceledException from CheckAsync (token cancel on rapid re-click or window close) bypasses the transition assignments, so the status returns to "Checking..." until the cooldown finally block clears it. Acceptable: a cancel-during-check user is the same user who clicked again, which is the path the cooldown is gating against. Resx Designer.cs regenerated. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
FarmLox
added a commit
that referenced
this pull request
May 25, 2026
The MissingFromDiskCount banner ("Windows refers to installer files
that aren't there. Cleaning the cache won't change this") fires for
two genuinely different populations:
- Registered, non-removable packages whose file is gone. Load-
bearing: an API-claimed file is gone, a future install /
uninstall / patch that needs it will fail. The banner text is
correct for this case.
- Superseded / obsoleted patches whose file is already gone (older
cleaner, manual sweep, prior PatchCleaner run). Benign: Windows
treats the patch as removable; the file having been removed is
the expected end state. The banner text reads false here ("Windows
refers" is wrong).
ScanResult splits MissingFromDiskCount into MissingNonRemovableCount
and MissingRemovableCount, with the existing MissingFromDiskCount kept
as a computed sum for ResultLogEntry's JSON (no schema change). The
banner condition switches to the non-removable count only.
ScanAsync_non_removable_missing_from_disk_counted_to_non_removable_bucket
covers the load-bearing case (was missing under the old shape: the
v1.8.1 audit (#3) called out the asymmetric coverage). The renamed
ScanAsync_superseded_patches_missing_from_disk_counted_to_removable_bucket
adds explicit MissingRemovableCount and MissingNonRemovableCount
assertions.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
FarmLox
added a commit
that referenced
this pull request
Jul 19, 2026
…checkout-6 chore(deps): bump actions/checkout from 4 to 6
FarmLox
added a commit
that referenced
this pull request
Jul 19, 2026
Closes the wontfix sentinel from the r4 review (ux-findings.md #1 and #3). The Check-for-updates button has been silent during its ~8-second in-flight wait since v1.5.0 and the r3 cooldown extended that silence by another 5 seconds; users on the failure path saw a dim button with no explanation and read it as broken. Screen- reader users got nothing at all. Two new resx strings: UpdateCheck.Status.Checking = "Checking..." UpdateCheck.Status.JustChecked = "Just checked." New TextBlock next to the Check-for-updates button in About, muted body type, AutomationProperties.LiveSetting=Polite so Narrator / NVDA / JAWS announce the transitions. State transitions in AboutWindow.xaml.cs CheckNowClick: click -> "Checking..." result dialog -> (unchanged; user reads MessageBox) dialog dismiss -> "Just checked." cooldown end -> "" OperationCanceledException from CheckAsync (token cancel on rapid re-click or window close) bypasses the transition assignments, so the status returns to "Checking..." until the cooldown finally block clears it. Acceptable: a cancel-during-check user is the same user who clicked again, which is the path the cooldown is gating against. Resx Designer.cs regenerated. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
FarmLox
added a commit
that referenced
this pull request
Jul 19, 2026
The MissingFromDiskCount banner ("Windows refers to installer files
that aren't there. Cleaning the cache won't change this") fires for
two genuinely different populations:
- Registered, non-removable packages whose file is gone. Load-
bearing: an API-claimed file is gone, a future install /
uninstall / patch that needs it will fail. The banner text is
correct for this case.
- Superseded / obsoleted patches whose file is already gone (older
cleaner, manual sweep, prior PatchCleaner run). Benign: Windows
treats the patch as removable; the file having been removed is
the expected end state. The banner text reads false here ("Windows
refers" is wrong).
ScanResult splits MissingFromDiskCount into MissingNonRemovableCount
and MissingRemovableCount, with the existing MissingFromDiskCount kept
as a computed sum for ResultLogEntry's JSON (no schema change). The
banner condition switches to the non-removable count only.
ScanAsync_non_removable_missing_from_disk_counted_to_non_removable_bucket
covers the load-bearing case (was missing under the old shape: the
v1.8.1 audit (#3) called out the asymmetric coverage). The renamed
ScanAsync_superseded_patches_missing_from_disk_counted_to_removable_bucket
adds explicit MissingRemovableCount and MissingNonRemovableCount
assertions.
Co-Authored-By: Claude Opus 4.7 (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.
Bumps actions/checkout from 4 to 6.
Release notes
Sourced from actions/checkout's releases.
... (truncated)
Changelog
Sourced from actions/checkout's changelog.
... (truncated)
Commits
de0fac2Fix tag handling: preserve annotations and explicit fetch-tags (#2356)064fe7fAdd orchestration_id to git user-agent when ACTIONS_ORCHESTRATION_ID is set (...8e8c483Clarify v6 README (#2328)033fa0dAdd worktree support for persist-credentials includeIf (#2327)c2d88d3Update all references from v5 and v4 to v6 (#2314)1af3b93update readme/changelog for v6 (#2311)71cf226v6-beta (#2298)069c695Persist creds to a separate file (#2286)ff7abcdUpdate README to include Node.js 24 support details and requirements (#2248)08c6903Prepare v5.0.0 release (#2238)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)