Preparation for release v2.0.0#10
Merged
Merged
Conversation
…Node version to 24
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.
What was done
Bug fixes
ignore_casedefault value inaction.ymlfromfalsetotrue, aligning it with the documented behaviour in the READMEignore_caseandfollow_symlinksdefault values from YAML booleans to strings, as required by the GitHub Actions input schemaignore_caseinput descriptionCI / Infrastructure
actions/checkoutfromv1tov4andactions/setup-nodefromv3tov4in all workflows22to24across all workflows to match thenode24runtime declared inaction.ymlyarn buildbeforenpx release-itin thereleasescript to ensuredist/is always up-to-date at release timeDocumentation
yarn release, and optional major tag updateNo upstream configured for current brancherror@v1references in README examples with@vX.X.XplaceholderTests
checkFileExistence, which previously had no coverage:getBooleanInputcalled with correct input names (Inputs.NO_CASE,Inputs.FOLLOW)true/falsebased on glob resultsnocaseandfollowoptions correctly forwarded to globConfig
**/*.test.tsfromtsconfig.jsonexcludeso the TypeScript language server correctly resolves the~/*path alias in test filesAlso closes #7