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

Use NPM clean install and upgrade node to v18 #8140

Merged
merged 1 commit into from
Feb 9, 2024

Conversation

steverep
Copy link
Member

@steverep steverep commented Feb 7, 2024

What do these changes do?

  • Installs llhttp using npm ci for security and to preserve the lock file. This command should always be used in CI.
  • Upgrades Node.js from v14 (out of maintenance) to v18 (current LTS maintenance release and also what the llhttp Dockerfile is using)

Are there changes in behavior for the user?

No

Is it a substantial burden for the maintainers to support this?

No

Related issue number

Fixes #8116

Checklist

  • I think the code is well written
  • Unit tests for the changes exist
  • Documentation reflects the changes
  • If you provide code modification, please add yourself to CONTRIBUTORS.txt
    • The format is <Name> <Surname>.
    • Please keep alphabetical order, the file is sorted by names.
  • Add a new news fragment into the CHANGES/ folder
    • name it <issue_or_pr_num>.<type>.rst (e.g. 588.bugfix.rst)

    • if you don't have an issue number, change it to the pull request
      number after creating the PR

      • .bugfix: A bug fix for something the maintainers deemed an
        improper undesired behavior that got corrected to match
        pre-agreed expectations.
      • .feature: A new behavior, public APIs. That sort of stuff.
      • .deprecation: A declaration of future API removals and breaking
        changes in behavior.
      • .breaking: When something public is removed in a breaking way.
        Could be deprecated in an earlier release.
      • .doc: Notable updates to the documentation structure or build
        process.
      • .packaging: Notes for downstreams about unobvious side effects
        and tooling. Changes in the test invocation considerations and
        runtime assumptions.
      • .contrib: Stuff that affects the contributor experience. e.g.
        Running tests, building the docs, setting up the development
        environment.
      • .misc: Changes that are hard to assign to any of the above
        categories.
    • Make sure to use full sentences with correct case and punctuation,
      for example:

      Fixed issue with non-ascii contents in doctest text files
      -- by :user:`contributor-gh-handle`.

      Use the past tense or the present tense a non-imperative mood,
      referring to what's changed compared to the last released version
      of this project.

@psf-chronographer psf-chronographer bot added the bot:chronographer:provided There is a change note present in this PR label Feb 7, 2024
Copy link

codecov bot commented Feb 7, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (8b33fe6) 97.41% compared to head (90343cb) 97.50%.
Report is 8 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #8140      +/-   ##
==========================================
+ Coverage   97.41%   97.50%   +0.09%     
==========================================
  Files         107      107              
  Lines       32732    32745      +13     
  Branches     3823     3829       +6     
==========================================
+ Hits        31885    31928      +43     
+ Misses        640      615      -25     
+ Partials      207      202       -5     
Flag Coverage Δ
CI-GHA 97.42% <100.00%> (+0.09%) ⬆️
OS-Linux 97.09% <100.00%> (+0.09%) ⬆️
OS-Windows 95.60% <100.00%> (+0.09%) ⬆️
OS-macOS 96.91% <100.00%> (+0.09%) ⬆️
Py-3.10.11 95.52% <100.00%> (+0.09%) ⬆️
Py-3.10.13 96.89% <100.00%> (+0.08%) ⬆️
Py-3.11.7 96.53% <100.00%> (+0.04%) ⬆️
Py-3.12.1 96.68% <100.00%> (+0.06%) ⬆️
Py-3.8.10 95.49% <100.00%> (+0.09%) ⬆️
Py-3.8.18 96.83% <100.00%> (+0.09%) ⬆️
Py-3.9.13 95.49% <100.00%> (+0.09%) ⬆️
Py-3.9.18 96.87% <100.00%> (+0.09%) ⬆️
Py-pypy7.3.15 96.40% <100.00%> (+0.06%) ⬆️
VM-macos 96.91% <100.00%> (+0.09%) ⬆️
VM-ubuntu 97.09% <100.00%> (+0.09%) ⬆️
VM-windows 95.60% <100.00%> (+0.09%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@Dreamsorcerer Dreamsorcerer merged commit d2ea811 into aio-libs:master Feb 9, 2024
31 of 34 checks passed
Copy link
Contributor

patchback bot commented Feb 9, 2024

Backport to 3.9: 💚 backport PR created

✅ Backport PR branch: patchback/backports/3.9/d2ea811853c2cb9305f7afe1a96265d31edb4f3b/pr-8140

Backported as #8149

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

patchback bot pushed a commit that referenced this pull request Feb 9, 2024
Copy link
Contributor

patchback bot commented Feb 9, 2024

Backport to 3.10: 💚 backport PR created

✅ Backport PR branch: patchback/backports/3.10/d2ea811853c2cb9305f7afe1a96265d31edb4f3b/pr-8140

Backported as #8150

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

patchback bot pushed a commit that referenced this pull request Feb 9, 2024
Dreamsorcerer pushed a commit that referenced this pull request Feb 9, 2024
…node to v18 (#8150)

**This is a backport of PR #8140 as merged into master
(d2ea811).**

Co-authored-by: Steve Repsher <[email protected]>
Dreamsorcerer pushed a commit that referenced this pull request Feb 9, 2024
…ode to v18 (#8149)

**This is a backport of PR #8140 as merged into master
(d2ea811).**

Co-authored-by: Steve Repsher <[email protected]>
@steverep steverep deleted the npm-ci-and-upgrade-node branch February 9, 2024 04:57
webknjaz added a commit to webknjaz/aiohttp that referenced this pull request Feb 16, 2024
…ia asyncio protocols

This is supposed to unify setting exceptions on the future objects,
allowing to also attach their causes whenever available. It'll make
possible for the end-users to see more detailed tracebacks.

It's also supposed to help with tracking down what's happening
with aio-libs#4581.

PR aio-libs#8089

Co-Authored-By: J. Nick Koston <[email protected]>
Co-Authored-By: Sam Bull <[email protected]>
(cherry picked from commit dc38630)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bot:chronographer:provided There is a change note present in this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Varying node versions & not using NPM clean install
2 participants