Repository navigation
feat: prepare setup-covdbg v1 with Node 24 - #2
Merged
Merged
Conversation
rwindegger
requested changes
Sep 21, 2026
rwindegger
approved these changes
Sep 21, 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
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.
Prepare setup-covdbg 1.0.0 for use as liasoft/setup-covdbg@v1 and move the action and its workflows to Node 24. Update checkout and setup-node to v6 and the release helper to v3 so the test and release workflows no longer depend on Node 20 actions.
The README documents v1 usage and the minimum runner version. The Windows test matrix exercises the committed action for both covdbg 1.3.0 and latest, checks the exact pinned version, and verifies PATH resolution, the covdbg-path output, and libcovdbg.dll. Repository and sample links point to liasoft and covdbg-quick-start.
Validation:
Release step: after merging this PR, run the Release workflow on main with version 1.0.0 to create v1.0.0 and v1. The tags are not created by the package version change itself; CONTRIBUTING.md documents the command.