Skip to content
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

Should the version of pnpm used to generate a shrinkwrap be checked in to vcs? #729

Closed
vjpr opened this issue Apr 26, 2017 · 2 comments
Closed

Comments

@vjpr
Copy link
Contributor

vjpr commented Apr 26, 2017

This relates to reproducible builds.

I see a version key in shrinkwrap.yaml, and I assume this is the version of the shrinkwrap schema?

The issue is that different versions of pnpm may have bugs or install different trees. Without knowing what version of pnpm was used to generate the shrinkwrap file there is the possibility that you get into a situation where you cannot reproduce your build.

I understand the reasoning of not having it in shrinkwrap.yaml because of churn if two users use different pnpm versions. But maybe its worth including it so that a build can always be reproduced if necessary in the rare case.

@zkochan
Copy link
Member

zkochan commented Apr 26, 2017

Good idea. There is currently a package-lock.json spec at npm and they also plan to have a created-with property.

@zkochan
Copy link
Member

zkochan commented May 13, 2017

Published with v0.68.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants