fix: resolve test failures in releases-github and process-lock#112
Merged
fix: resolve test failures in releases-github and process-lock#112
Conversation
- Guard against missing assets array in GitHub release API response - Fix test mock to cover retry attempts in getReleaseAssetUrl - Fix Windows path separator handling in process-lock directory creation
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
1 participant
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.
Summary
assetsarray in GitHub release API response to preventCannot read properties of undefinedcrashlastIndexOf('/')missed\separators, causing ENOENT on nested lock pathsmockResolvedValueinstead ofmockResolvedValueOnceso retry attempts get valid responsesTest plan
releases-github.test.mts— "should throw error when pattern does not match any asset" passesdlx/manifest.test.mts— "should create manifest directory if it does not exist" passes on Windows