chore: update dependencies#4162
Merged
Merged
Conversation
Collaborator
|
I think we should wait for the upstream fix, there is no need to have the newest node v26 version in the workflow. Beside this I opened an additional issue which got a new status |
Collaborator
Author
|
Totally fine with dropping the workaround. Just reduced the PR to the dependency updates. This should solve some of the dependabot alerts. |
KristjanESPERANTO
changed the title
khassel
approved these changes
May 20, 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.
This updates the dependencies and implements a workaround for the failing ci tests on node 26.1.0 (#4150).
I'm not sure myself whether we should go with this workaround or wait for an upstream fix.