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

fix: lerna version maintains package-lock #14

Merged
merged 1 commit into from Nov 14, 2019

Conversation

seebees
Copy link
Contributor

@seebees seebees commented Nov 14, 2019

resolves #13

Lerna version 3.18.2 will version package-lock.json files.
This means that if they are in .gitingnore the version command will fail.
Better visibility into versions should help debugging.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

resolves aws#13

Lerna version 3.18.2 will version package-lock.json files.
This means that if they are in .gitingnore the version command will fail.
Better visibility into versions should help debugging.
@seebees seebees requested review from agray256 and a team November 14, 2019 19:01
@@ -9,8 +9,6 @@
# Artifacts
build
node_modules
package-lock.json
package.json.decrypt
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What does the package.json.decrypt file do? That sounds like something that might be good to keep out of version control.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In trying to work out what was going wrong,
we synced the .gitignore files from the ESDK JS.

This is from that file.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

<from offline discussion/>

Specifically, it sounds like this was something that we added because of an artifact that a manual test created, not something that we expect to ever exist again.

I wanted to make sure that we were not blindly removing something that was protecting us from an unintended leak from a build tool or similar.

Copy link
Contributor

@agray256 agray256 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. verified w/ npm install; npm run bootstrap; npm test; npx lerna version --conventional-commits --yes --no-push

@seebees seebees merged commit 2ef29e1 into aws:master Nov 14, 2019
@seebees seebees deleted the add_package-lock branch November 14, 2019 21:06
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

Successfully merging this pull request may close these issues.

Add package-lock.json to source control
3 participants