-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting issue with deploy code with latest version #355
Comments
Hi @parvindersarora1 , we experience the same issue. We tried the previous version https://github.com/SalesforceCommerceCloud/sfcc-ci/releases/tag/v2.10.0 but have the same error. So assuming that this is somehow related to bitbucket pipelines. We workarounded by using |
i am facing the same issue while installing sfcc-ci "npm install -g sfcc-ci" with image "node:lts-fermium" on gitlab pipeline (gitlab-runner 15.9.0~beta.115.g598a7c91). My temp solution was to disable postinstall scripts:
But I'm not sure what other implications that might have. |
Me too, npm install -g sfcc-ci wont run on my GitLab Pipeline. The image um using: image: node:lts-fermium. The Problem seems, that a sub dependency called "snyk" updated released a new version yesterday. The latest Version [email protected] seems causing my current problems: |
Hi @parvindersarora1 @stm-dschulz @dev-niko @ricardoseifert , we've an open PR #470 which (hopefully) will fix this issue. Can you give that a try and provide feedback please? |
Hi @tobiaslohr, |
Thanks @stm-dschulz! @parvindersarora1 Can you please re-test on your side as well? PR #470 was merged into master, though no release has been built with that yet. |
sfcc-ci Version
2.11.0
NodeJS Version
14.17.6
sfcc-ci Path
Bitbucket on linux
Host OS Details
Not sure it is issue on bitbucket
Description
Getting issue with sfcc-ci@latest version. Nothing change on pipeline or package only issue comes after latest version with sfcc-ci. Our last successful build was done 8 days earlier.
Relevant log output
The text was updated successfully, but these errors were encountered: