Merged
Conversation
Collaborator
|
Thank you @janbrasna for your contribution ⭐ |
Contributor
Author
|
Ooh anytime, this is so nice with the stream of green in the pipeline — thanks for taking care of keeping it all so up to date (and already having resolved the deprecations, w00t!!), lovely work! (I still haven't figured out what was supposed to be failing the CI runs in the first place, as this kitty purrs happily … but given dep resolution shifts over time in CI/runners anyways, I'm just glad it wasn't really anything;)…) |
Contributor
Author
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
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 refreshes the CI, and updates a few spots around it.
The last actions runs appear logged with failure; I wasn't able to reproduce, the CI seems currently passing. For good measure I removed the empty file test artifact, and added current active (future LTS) Node version for visibility.
I removed any cache restoring from release pipeline for security reasons.
(Generally the ~5sec saved in reusing cached packages is spent on ~5sec restoring caches, so… 🤷)
There were a few CI status badges, incl. on the readme published to a package npmjs page, so I updated these to use current format.
Tested for both windows-2022 and windows-2025 whatever gets picked up as the latest tag runner.
NB: This recent Node 24 addition sheds some light on future deprecations: