fix: Fixing cache load step breaking when no lock file is detected #200
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.
If your project does not contain any lockfile at all, this logic falls through and does not copy anything to
$TARGET_DIR/node-project-lockfile
:node-orb/src/scripts/packages/determine-lockfile.sh
Lines 6 to 16 in ab05d0e
However, if you run this without
with-cache: false
, this step fails:node-orb/src/commands/install-packages.yml
Line 70 in ab05d0e
As:
Expected behavior:
Caching step should complete without a lockfile present.