You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
On November 8th, a new version of the netlify-cli npm package (17.2.0) was released. When pulled into CI runs, it began causing issues on our warehouse build task. At the time of writing, the cause has yet to be identified, so we pinned the version we use to 17.1.0 to keep CI running while we investigate further.
To Reproduce
If you unpin the version of netlify-cli referenced in our warehouse Dockerfile, CI will fail to build the warehouse (at least while 17.2.0 is still the active latest version).
Expected behavior
Our builds should function normally using the latest version of the netlify-cli package, if possible.
Additional context
The fix may be on the package side - we might need to wait for a new version of netlify-cli to publish and then simply unpin. At the time of writing, I haven't investigated closely enough to learn whether we can solve the issue on our side without using an older version of the tool.
The text was updated successfully, but these errors were encountered:
Describe the bug
On November 8th, a new version of the
netlify-cli
npm package (17.2.0) was released. When pulled into CI runs, it began causing issues on our warehouse build task. At the time of writing, the cause has yet to be identified, so we pinned the version we use to 17.1.0 to keep CI running while we investigate further.To Reproduce
If you unpin the version of
netlify-cli
referenced in our warehouse Dockerfile, CI will fail to build the warehouse (at least while 17.2.0 is still the active latest version).Expected behavior
Our builds should function normally using the latest version of the
netlify-cli
package, if possible.Additional context
The fix may be on the package side - we might need to wait for a new version of
netlify-cli
to publish and then simply unpin. At the time of writing, I haven't investigated closely enough to learn whether we can solve the issue on our side without using an older version of the tool.The text was updated successfully, but these errors were encountered: