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

build: add node v18 support #847

Merged
merged 3 commits into from
May 3, 2022
Merged

build: add node v18 support #847

merged 3 commits into from
May 3, 2022

Conversation

Shinigami92
Copy link
Member

@Shinigami92 Shinigami92 commented Apr 20, 2022

  • Use node v18 as new default
  • Still support v14 and v16, v16 specially as latest LTS
  • Remove support for node v12 completely (maybe we can do this in a separate PR if we need to long for other v6.x stuff) see build!: remove node v12 support #850

@Shinigami92 Shinigami92 added c: chore PR that doesn't affect the runtime behavior p: 1-normal Nothing urgent labels Apr 20, 2022
@Shinigami92 Shinigami92 added this to the v6 - Non-Breaking Changes milestone Apr 20, 2022
@Shinigami92 Shinigami92 self-assigned this Apr 20, 2022
@codecov
Copy link

codecov bot commented Apr 20, 2022

Codecov Report

Merging #847 (4353b76) into main (18614fb) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #847      +/-   ##
==========================================
- Coverage   99.64%   99.64%   -0.01%     
==========================================
  Files        1958     1958              
  Lines      210679   210679              
  Branches      908      907       -1     
==========================================
- Hits       209934   209931       -3     
- Misses        726      729       +3     
  Partials       19       19              
Impacted Files Coverage Δ
src/modules/finance/index.ts 99.31% <0.00%> (-0.69%) ⬇️

package.json Outdated Show resolved Hide resolved
@Shinigami92 Shinigami92 added the s: on hold Blocked by something or frozen to avoid conflicts label Apr 20, 2022
@Shinigami92
Copy link
Member Author

According to this table https://kangax.github.io/compat-table/es2016plus/#node14_0 I think we can also switch to target 2020 🥳
maybe in a separate PR

@Shinigami92 Shinigami92 changed the title ci: use node 18 build: add node v18 support Apr 20, 2022
@Shinigami92 Shinigami92 removed the s: on hold Blocked by something or frozen to avoid conflicts label Apr 20, 2022
@Shinigami92 Shinigami92 linked an issue Apr 21, 2022 that may be closed by this pull request
@Shinigami92 Shinigami92 marked this pull request as ready for review May 3, 2022 15:30
@Shinigami92 Shinigami92 requested a review from a team May 3, 2022 15:30
@Shinigami92 Shinigami92 requested a review from a team as a code owner May 3, 2022 15:30
@ST-DDT
Copy link
Member

ST-DDT commented May 3, 2022

This probably need admin powers to be merged.

@Shinigami92 Shinigami92 requested review from a team May 3, 2022 17:16
@Shinigami92 Shinigami92 merged commit e29e875 into main May 3, 2022
@Shinigami92 Shinigami92 deleted the node-18 branch May 3, 2022 18:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c: chore PR that doesn't affect the runtime behavior p: 1-normal Nothing urgent
Projects
No open projects
Status: Done
Development

Successfully merging this pull request may close these issues.

FEAT: Support Node18 when it drops
3 participants