Update actions - #483
Merged
Merged
Conversation
With pnpm v11 this could and should be replaced with pnpm/setup, I guess.
It looks like this should be non-critical, it mainly includes a runtime upgrade to Node 24 as far as I could see that.
I think this is also non-critical and mainly a runtime bump.
Should also be just the node version bump.
This is quite a jump and I'm not very familiar with this action. But the changelogs looked more or less not critical, there was only a thing about downloading single artifacts by id in v5, but I think the "No Action Needed If" applies.
DecDuck
approved these changes
Aug 30, 2026
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
2 participants
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.
I noticed some warnings in the CI, that some things still use Node 20 which is deprecated. I therefore updated most actions in the repo. I checked the changelogs and THINK that everything on a critical path like the release should still work, but I guess we can only be sure on the next run 😅 Therefore I'm of course open to removing some updates on those paths.
I also skipped
tauri-apps/tauri-actionbecause I think this could break, if I read the changelog for v1.I'm not sure, if the decision to not handle updating github actions is a deliberate one, therefore I didn't do it in this PR, but Dependabot could do these updates for you (or at least open PRs for it), if you want via the
github-actionsecosystem. For that a.github/dependabot.ymlwould be needed.