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: node-please-upgrade usage #575

Merged
merged 2 commits into from Feb 2, 2019
Merged

Conversation

julien-f
Copy link
Contributor

@julien-f julien-f commented Feb 1, 2019

Before: undefined requires at least version 8.6.0 of Node, please upgrade
After: lint-staged requires at least version 8.6.0 of Node, please upgrade

@codecov
Copy link

codecov bot commented Feb 1, 2019

Codecov Report

Merging #575 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #575   +/-   ##
=======================================
  Coverage   98.14%   98.14%           
=======================================
  Files          13       13           
  Lines         378      378           
  Branches       52       52           
=======================================
  Hits          371      371           
  Misses          7        7

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 8c4d9c9...56fcbf2. Read the comment docs.

Copy link
Collaborator

@okonet okonet left a comment

Choose a reason for hiding this comment

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

Let’s add the name to the object in the JS file to fix the output and leave package.json alone.

package.json Outdated
@@ -10,6 +10,9 @@
"Suhas Karanth <sudo.suhas@gmail.com>"
],
"bin": "index.js",
"engines": {
"node": ">=8.6.0"
Copy link
Collaborator

Choose a reason for hiding this comment

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

That’s was intentional not to have it here since it would break CIs with lower versions of Node installed without a particular reason. I’m on my mobile so I can’t search for the issue but please look for it.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I see, too bad we can't have optional dev deps 😞

We should at least pass the name to node-please-upgrade to avoid broken message.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Yes that’s what I’m keen to merge. Could you please update the PR? Thanks!

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed.

Before: `undefined requires at least version 8.6.0 of Node, please upgrade`
After: `lint-staged requires at least version 8.6.0 of Node, please upgrade`
@julien-f julien-f changed the title fix: declare compat in package.engines and fix node-please-upgrade usage fix: node-please-upgrade usage Feb 2, 2019
@okonet
Copy link
Collaborator

okonet commented Feb 2, 2019

Hmm could you please check why is CI failing now?

@julien-f
Copy link
Contributor Author

julien-f commented Feb 2, 2019

I think it's because I pushed too quickly and GitHub/Travis mixed things up a bit, because the tests passed: https://travis-ci.org/okonet/lint-staged/pull_requests

@okonet okonet merged commit f5bed7b into lint-staged:master Feb 2, 2019
@okonet
Copy link
Collaborator

okonet commented Feb 2, 2019

Thanks for working on this!

@okonet
Copy link
Collaborator

okonet commented Feb 2, 2019

🎉 This PR is included in version 8.1.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

@okonet okonet added the released label Feb 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

None yet

2 participants