`windows-2025` compatibility

[kdeldycke]

I was using install-winget for a year on windows-2022 runners and it worked perfectly fine!

Then I bumped my runner to windows-2025 and it seems WinGet can be installed there just fine with the vanilla command:

$ winget upgrade winget --accept-package-agreements --accept-source-agreements --disable-interactivity

If confirmed, maybe we can add a note at the top of this project readme to indicate that this action workaround is no longer necessary for windows-2025 targets.

Also see the relevant comment on winget-cli project at: microsoft/winget-cli#3872 (comment)

[Cyberboss]

Probably going to implement that for 2025 targets and then archive this project. It was always a workaround for the installation experience just being absolute trash and if it's working now then it's not really necessary any more.

[Cyberboss]

Seems to be too sporadic currently https://github.com/Cyberboss/install-winget/actions/runs/14283352800/job/40035477451

[eythaann]

x2 I was having this same issue since today; I'm updating all my workflows now.

[kdeldycke]

Seems to be too sporadic currently https://github.com/Cyberboss/install-winget/actions/runs/14283352800/job/40035477451

Ah yes, WinGet CLI exit with an error code if it doesn't find an upgrade available. With is completely fine because it means WinGet is installed and already up-to-date on the runner.

I stumbled upon this exact same issue and choose to simply ignore the error if WinGet fails to be updated:

$ winget upgrade winget --accept-package-agreements --accept-source-agreements --disable-interactivity || & { "ignore failure"; $global:LASTEXITCODE = 0 }