Problem with 2.2.23 npm release?

[real34]

Problem with 2.2.23 npm release?

[danpaz]

I've published 2.2.25 which includes the lib files and should fix the issue. Could someone confirm please?

[danpaz]

@uyu423 I'm thinking I'll actually unpublish those two versions since they're completely broken.

[uyu423]

We have same problem.....

[antick]

I am facing the same issue.

[alattalatta]

the lib directory is gone.

Fixing the version to 2.2.22 fixed it.

[StevenStreib]

I have the same issue.

[pranav-aggarwal]

Same issue with latest release.

[uyu423]

I had a problem with a project using this library, and I fixed this issue by changing the version of package.json from bodybuilder@^2.22.20 to [email protected] fixed version. This update looks very unstable.

[danpaz]

Looks like something broke with the last few publishes. Looking into it now, but yes the immediate workaround is to use v2.2.22.

[ferronrsmith]

works for me

[uyu423]

@danpaz
First of all, you need to take steps to ensure that the problematic version is no longer downloaded.
Please deprecate the currently problematic version from npm.

npm deprecate [email protected] "critical bug fixed"
npm deprecate [email protected] "critical bug fixed"

[uyu423]

@danpaz You are right.

[danpaz]

Missed the deadline to unpublish so I went ahead and deprecated 2.2.23 and 2.2.24.

As for what caused the breakage, it seems travis ci deployment changed recently and started logging in the deploy step:

Cleaning up git repository with `git stash --all`. If you need build artifacts for deployment, set `deploy.skip_cleanup: true`. See https://docs.travis-ci.com/user/deployment#Uploading-Files-and-skip_cleanup.

The travis build does produce untracked files, such as those in lib, which are necessary for the package to work.

ccf0f71 adds deploy.skip_cleanup: true as recommended and should fix the issue moving forward.

Thanks for reporting @real34 and others 🙇

[real34]

Thanks a lot for your responsiveness, and for your work on this project! 👍