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

feat(node): update version number in package-lock.json #467

Merged
merged 1 commit into from Jun 17, 2020

Conversation

socsieng
Copy link
Contributor

@socsieng socsieng commented Jun 14, 2020

Keep version number in package-lock.json in sync with package.json.

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

  • Make sure to open an issue as a bug/issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
  • Ensure the tests and linter pass
  • Code coverage does not decrease (if any source code was changed)
  • Appropriate docs were updated (if necessary)

Fixes #464

I had some time to kill so I thought I would implement this PR despite the issue still being in triage. I know there is a chance that updating package-lock.json isn't the desired behavior, but I did have some time to kill and understand if issue #464 and this PR are declined.

@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label Jun 14, 2020
@codecov
Copy link

codecov bot commented Jun 14, 2020

Codecov Report

Merging #467 into master will increase coverage by 1.58%.
The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #467      +/-   ##
==========================================
+ Coverage   79.79%   81.37%   +1.58%     
==========================================
  Files          40       40              
  Lines        4657     4666       +9     
  Branches      377      382       +5     
==========================================
+ Hits         3716     3797      +81     
+ Misses        940      868      -72     
  Partials        1        1              
Impacted Files Coverage Δ
src/releasers/node.ts 93.28% <100.00%> (+58.08%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 301a08a...00c2fb5. Read the comment docs.

@bcoe
Copy link
Contributor

bcoe commented Jun 14, 2020

@socsieng thanks for the contribution, happen to be doing some triage myself today and was excited to see this 😄

Will work on landing it early this week.

Copy link
Contributor

@bcoe bcoe left a comment

Choose a reason for hiding this comment

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

Left a few initial comments, this is looking great to me.

src/releasers/node.ts Outdated Show resolved Hide resolved
test/releasers/node.ts Outdated Show resolved Hide resolved
test/releasers/node.ts Outdated Show resolved Hide resolved
test/releasers/node.ts Outdated Show resolved Hide resolved
@socsieng socsieng force-pushed the package-lock branch 3 times, most recently from d6502cc to f488a35 Compare June 15, 2020 02:36
Keep version number in package-lock.json in sync with package.json.

Fixes: googleapis#464
@bcoe bcoe added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jun 15, 2020
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jun 15, 2020
@bcoe bcoe merged commit 2d69956 into googleapis:master Jun 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes This human has signed the Contributor License Agreement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update version number in package-lock.json to match package.json
4 participants