Skip to content

chore(dev-deps): bump @types/node to 12.20.7 #3012

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

Merged
merged 1 commit into from
Apr 2, 2021
Merged

Conversation

jsjoeio
Copy link
Contributor

@jsjoeio jsjoeio commented Mar 31, 2021

This PR bumps @types/node to 12.20.7

Tested locally using node 12.20.2 and everything works as expected.

Related:

@jsjoeio jsjoeio requested a review from a team as a code owner March 31, 2021 23:14
@jsjoeio jsjoeio changed the title chore: bump @types/node to 12.20.7 chore(dev-deps): bump @types/node to 12.20.7 Mar 31, 2021
@jsjoeio jsjoeio self-assigned this Mar 31, 2021
@jsjoeio jsjoeio added this to the v3.9.3 milestone Mar 31, 2021
@jsjoeio jsjoeio marked this pull request as draft April 1, 2021 16:54
@jsjoeio jsjoeio force-pushed the jsjoeio/bump-types-node branch from 9f30ae5 to c7d7041 Compare April 1, 2021 16:55
@jsjoeio jsjoeio marked this pull request as ready for review April 1, 2021 16:57
@@ -41,7 +41,7 @@
"@types/express": "^4.17.8",
"@types/http-proxy": "^1.17.4",
"@types/js-yaml": "^4.0.0",
"@types/node": "^12.12.7",
"@types/node": "~12.20.7",
Copy link

Choose a reason for hiding this comment

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

Not sure if ~ is intentional here to keep us on the 12.20.x series instead of the 12.x series (which would be behavior for ^) - @jsjoeio

Copy link
Contributor Author

@jsjoeio jsjoeio Apr 2, 2021

Choose a reason for hiding this comment

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

It was made intentionally! I was thinking we should stay on 12.20.x series but open to changing it if you think that's the wrong move!

Copy link

Choose a reason for hiding this comment

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

I don't know enough about @types/node to know for sure, I think I'd defer to your judgements, though feel free to pull in asher for another opinion!

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 think it's okay then. I think we make it strict like this with ~ and if that's the wrong move, then we reverse it. Easily reversible!

Copy link
Member

Choose a reason for hiding this comment

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

Since we support a range of Node versions I'm not really sure what versions of the types we should use.

I suppose we should keep it in sync with whatever we use to build in CI? So if we use Node 12.20.x then we use 12.20.x types, etc.

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'm in agreement! Sounds good to me!

@jsjoeio jsjoeio force-pushed the jsjoeio/bump-types-node branch from c7d7041 to c415fd2 Compare April 2, 2021 19:46
@jsjoeio jsjoeio enabled auto-merge April 2, 2021 19:46
@jsjoeio jsjoeio merged commit 5a1ea2c into main Apr 2, 2021
@jsjoeio jsjoeio deleted the jsjoeio/bump-types-node branch April 2, 2021 21:07
@jsjoeio jsjoeio added the chore Related to maintenance or clean up label May 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Related to maintenance or clean up
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants