Update continuous-integration-workflow.yml #1237
Merged
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.
JIRA link
https://hee-tis.atlassian.net/browse/TD-5768
Description
Since it’s working in Azure DevOps, I mirrored that setup by using Azure DevOps as well—just running the build with npm instead of yarn
Previously, yarn install (without yarn.lock) pulled in transitive dependencies like @types/minimatch implicitly — and it just worked.
But now, some upstream package (or its types) may have:
Dropped or altered minimatch typings
Removed @types/minimatch from its dependencies or peerDependencies
As a result, the same workflow now breaks because minimatch is still expected, but not resolved.
Screenshots
Paste screenshots for all views created or changed: mobile, tablet and desktop, wave analyser showing no errors.
Developer checks
(Leave tasks unticked if they haven't been appropriate for your ticket.)
I have:
Either:
Or: