Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

chore(deps): update all non-major dependencies#178

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
renovate wants to merge1 commit intodev
base:dev
Choose a base branch
Loading
fromrenovate/all-minor-patch

Conversation

@renovate
Copy link
Contributor

@renovaterenovatebot commentedJan 6, 2021
edited
Loading

This PR contains the following updates:

PackageChangeAgeConfidenceTypeUpdate
@nuxt/content-theme-docs^0.8.2 ->^0.11.1ageconfidencedependenciesminor
consola^2.15.0 ->^2.15.3ageconfidencedependenciespatch
minimatch^3.0.4 ->^3.1.2ageconfidencedependenciesminor
node (source)>=8.9.0 ->>=8.17.0ageconfidenceenginesminor
npm (source)>=5.0.0 ->>=5.10.0ageconfidenceenginesminor
nuxt (source)^2.14.11 ->^2.18.1ageconfidencedependenciesminor

Release Notes

nuxt/content (@​nuxt/content-theme-docs)

v0.11.1

Compare Source

v0.11.0

Compare Source

v0.10.2

Compare Source

v0.10.1

Compare Source

v0.10.0

Compare Source

v0.9.0

Compare Source

unjs/consola (consola)

v2.15.3

Compare Source

v2.15.2

Compare Source

v2.15.1

Compare Source

isaacs/minimatch (minimatch)

v3.1.2

Compare Source

v3.1.1

Compare Source

v3.1.0

Compare Source

v3.0.8

Compare Source

v3.0.7

Compare Source

v3.0.6

Compare Source

v3.0.5

Compare Source

nodejs/node (node)

v8.17.0: 2019-12-17, Version 8.17.0 'Carbon' (LTS), @​MylesBorins

Compare Source

This is a security release.

For more details about the vulnerability please consult the npm blog:

https://blog.npmjs.org/post/189618601100/binary-planting-with-the-npm-cli

Notable changes
Commits

v8.16.2: 2019-10-09, Version 8.16.2 'Carbon' (LTS), @​BethGriggs

Compare Source

Node.js 8 is due to go End-of-Life on 31st December 2019.

Notable changes
  • deps: upgrade openssl sources to 1.0.2s (Sam Roberts)#​28230
Commits

v8.16.1: 2019-08-15, Version 8.16.1 'Carbon' (LTS), @​BethGriggs

Compare Source

Notable changes

This is a security release.

Node.js, as well as many other implementations of HTTP/2, have been found
vulnerable to Denial of Service attacks.
Seehttps://github.com/Netflix/security-bulletins/blob/master/advisories/third-party/2019-002.md
for more information.

Vulnerabilities fixed:

  • CVE-2019-9511 “Data Dribble”: The attacker requests a large amount of data from a specified resource over multiple streams. They manipulate window size and stream priority to force the server to queue the data in 1-byte chunks. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both, potentially leading to a denial of service.
  • CVE-2019-9512 “Ping Flood”: The attacker sends continual pings to an HTTP/2 peer, causing the peer to build an internal queue of responses. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both, potentially leading to a denial of service.
  • CVE-2019-9513 “Resource Loop”: The attacker creates multiple request streams and continually shuffles the priority of the streams in a way that causes substantial churn to the priority tree. This can consume excess CPU, potentially leading to a denial of service.
  • CVE-2019-9514 “Reset Flood”: The attacker opens a number of streams and sends an invalid request over each stream that should solicit a stream of RST_STREAM frames from the peer. Depending on how the peer queues the RST_STREAM frames, this can consume excess memory, CPU, or both, potentially leading to a denial of service.
  • CVE-2019-9515 “Settings Flood”: The attacker sends a stream of SETTINGS frames to the peer. Since the RFC requires that the peer reply with one acknowledgement per SETTINGS frame, an empty SETTINGS frame is almost equivalent in behavior to a ping. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both, potentially leading to a denial of service.
  • CVE-2019-9516 “0-Length Headers Leak”: The attacker sends a stream of headers with a 0-length header name and 0-length header value, optionally Huffman encoded into 1-byte or greater headers. Some implementations allocate memory for these headers and keep the allocation alive until the session dies. This can consume excess memory, potentially leading to a denial of service.
  • CVE-2019-9517 “Internal Data Buffering”: The attacker opens the HTTP/2 window so the peer can send without constraint; however, they leave the TCP window closed so the peer cannot actually write (many of) the bytes on the wire. The attacker then sends a stream of requests for a large response object. Depending on how the servers queue the responses, this can consume excess memory, CPU, or both, potentially leading to a denial of service.
  • CVE-2019-9518 “Empty Frames Flood”: The attacker sends a stream of frames with an empty payload and without the end-of-stream flag. These frames can be DATA, HEADERS, CONTINUATION and/or PUSH_PROMISE. The peer spends time processing each frame disproportionate to attack bandwidth. This can consume excess CPU, potentially leading to a denial of service. (Discovered by Piotr Sikora of Google)
Commits

v8.16.0: 2019-04-16, Version 8.16.0 'Carbon' (LTS), @​MylesBorins

Compare Source

Notable Changes
  • n-api:
    • add API for asynchronous functions (Gabriel Schulhof)#​17887
    • mark thread-safe function as stable (Gabriel Schulhof)#​25556
Commits

v8.15.1

Compare Source

v8.15.0: 2018-12-26, Version 8.15.0 'Carbon' (LTS), @​MylesBorins

Compare Source

The 8.14.0 security release introduced some unexpected breakages on the 8.x release line.
This is a special release to fix a regression in the HTTP binary upgrade response body and add
a missing CLI flag to adjust the max header size of the http parser.

Notable Changes
  • cli:
    • add --max-http-header-size flag (cjihrig)#​24811
  • http:
    • add maxHeaderSize property (cjihrig)#​24860
Commits

v8.14.1: 2018-12-18, Version 8.14.1 'Carbon' (LTS), @​MylesBorins prepared by @​BethGriggs

Compare Source

Notable changes
  • assert:
    • revert breaking change (Ruben Bridgewater)#​24786
  • http2:
    • fix sequence of error/close events (Gerhard Stoebich)#​24789
Commits

v8.14.0: 2018-11-27, Version 8.14.0 'Carbon' (LTS), @​rvagg

Compare Source

This is a security release. All Node.js users should consult the security release summary at:

https://nodejs.org/en/blog/vulnerability/november-2018-security-releases/

for details on patched vulnerabilities.

Fixes for the following CVEs are included in this release:

  • Node.js: Denial of Service with large HTTP headers (CVE-2018-12121)
  • Node.js: Slowloris HTTP Denial of Service (CVE-2018-12122 / Node.js)
  • Node.js: Hostname spoofing in URL parser for javascript protocol (CVE-2018-12123)
  • Node.js: HTTP request splitting (CVE-2018-12116)
  • OpenSSL: Timing vulnerability in DSA signature generation (CVE-2018-0734)
  • OpenSSL: Microarchitecture timing vulnerability in ECC scalar multiplication (CVE-2018-5407)
Notable Changes
  • deps: Upgrade to OpenSSL 1.0.2q, fixingCVE-2018-0734 andCVE-2018-5407
  • http:
    • Headers received by HTTP servers must not exceed 8192 bytes in total to prevent possible Denial of Service attacks. Reported by Trevor Norris. (CVE-2018-12121 / Matteo Collina)
    • A timeout of 40 seconds now applies to servers receiving HTTP headers. This value can be adjusted withserver.headersTimeout. Where headers are not completely received within this period, the socket is destroyed on the next received chunk. In conjunction withserver.setTimeout(), this aids in protecting against excessive resource retention and possible Denial of Service. Reported by Jan Maybach (liebdich.com). (CVE-2018-12122 / Matteo Collina)
    • Two-byte characters are now strictly disallowed for thepath option in HTTP client requests. Paths containing characters outside of the range\u0021 -\u00ff will now be rejected with aTypeError. This behavior can be reverted if necessary by supplying the--security-revert=CVE-2018-12116 command line argument (this is not recommended). Reported as security concern for Node.js 6 and 8 byArkadiy Tetelman (Lob), fixed by backporting a change by Benno Fünfstück applied to Node.js 10 and later. (CVE-2018-12116 / Matteo Collina)
  • url: Fix a bug that would allow a hostname being spoofed when parsing URLs withurl.parse() with the'#"https://twitter.com/_bayotop" rel="nofollow">Martin Bajanik (Kentico). (CVE-2018-12123 / Matteo Collina)
Commits

v8.13.0: 2018-11-20, Version 8.13.0 'Carbon' (LTS), @​MylesBorins prepared by @​BethGriggs

Compare Source

Notable changes
  • assert:
    • backport some assert commits (Ruben Bridgewater)#​23223
  • deps:
    • upgrade to libuv 1.23.2 (cjihrig)#​23336
    • V8: cherry-pick 64-bit hash seed commits (Yang Guo)#​23274
  • http:
    • added aborted property to request (Robert Nagy)#​20094
  • http2:
    • graduate from experimental (James M Snell)#​22466
Commits

Configuration

📅Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻Immortal: This PR will be recreated if closed unmerged. Getconfig help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated byMend Renovate. View therepository job log.

@codecov
Copy link

codecovbot commentedJan 6, 2021
edited
Loading

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base(0bc0ebd) to head(bb49f87).
Report is 3 commits behind head on dev.

Current headbb49f87 differs from pull request most recent headaa26f1d

Pleaseupload reports for the commitaa26f1d to get more accurate results.

Additional details and impacted files
@@            Coverage Diff            @@##               dev      #178   +/-   ##=========================================  Coverage   100.00%   100.00%           =========================================  Files            7         7             Lines          261       261             Branches        57        57           =========================================  Hits           261       261

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

@renovaterenovatebotforce-pushed therenovate/all-minor-patch branch from9dd7bdf to60450d1CompareFebruary 3, 2021 11:55
@renovaterenovatebot changed the titlechore(deps): update dependency nuxt to ^2.14.12chore(deps): update all non-major dependenciesFeb 3, 2021
@renovaterenovatebotforce-pushed therenovate/all-minor-patch branch 4 times, most recently fromd47a225 to18de832CompareFebruary 15, 2021 11:43
@renovaterenovatebotforce-pushed therenovate/all-minor-patch branch from18de832 to6f6a565CompareApril 26, 2021 12:42
@renovaterenovatebotforce-pushed therenovate/all-minor-patch branch 2 times, most recently froma4fed2f tocb33e29CompareMay 15, 2021 19:13
@renovaterenovatebotforce-pushed therenovate/all-minor-patch branch fromcb33e29 to9ccb3b8CompareJune 14, 2021 21:09
@renovaterenovatebotforce-pushed therenovate/all-minor-patch branch 2 times, most recently fromab32f4b tobb49f87CompareOctober 21, 2021 11:53
@renovaterenovatebotforce-pushed therenovate/all-minor-patch branch frombb49f87 to57020c7CompareNovember 17, 2021 13:11
@renovaterenovatebotforce-pushed therenovate/all-minor-patch branch from57020c7 to442173aCompareMarch 7, 2022 17:02
@renovaterenovatebotforce-pushed therenovate/all-minor-patch branch from442173a toaa54883CompareMarch 18, 2023 04:10
@renovaterenovatebotforce-pushed therenovate/all-minor-patch branch fromaa54883 to47f6a3eCompareJune 9, 2023 23:00
@renovaterenovatebotforce-pushed therenovate/all-minor-patch branch from47f6a3e to1d0b1adCompareJuly 14, 2023 22:51
@renovaterenovatebotforce-pushed therenovate/all-minor-patch branch from1d0b1ad to11163bfCompareSeptember 19, 2023 15:15
@renovaterenovatebotforce-pushed therenovate/all-minor-patch branch from11163bf tod39fec4CompareOctober 24, 2023 03:57
@renovaterenovatebotforce-pushed therenovate/all-minor-patch branch fromd39fec4 to65f9effCompareJanuary 12, 2024 15:41
@renovaterenovatebotforce-pushed therenovate/all-minor-patch branch from65f9eff to6e5a3c7CompareJune 14, 2024 14:42
@renovaterenovatebotforce-pushed therenovate/all-minor-patch branch 2 times, most recently from90af95a toaa26f1dCompareJune 28, 2024 14:17
@renovaterenovatebotforce-pushed therenovate/all-minor-patch branch 2 times, most recently froma332f89 todea14b4CompareAugust 13, 2025 12:50
@renovaterenovatebotforce-pushed therenovate/all-minor-patch branch fromdea14b4 to70b7ae5CompareAugust 19, 2025 12:11
@renovaterenovatebotforce-pushed therenovate/all-minor-patch branch from70b7ae5 to09b292fCompareAugust 31, 2025 11:34
@renovaterenovatebotforce-pushed therenovate/all-minor-patch branch from09b292f to7d7ddcbCompareSeptember 25, 2025 18:07
@renovaterenovatebotforce-pushed therenovate/all-minor-patch branch from7d7ddcb tob42d1ccCompareOctober 21, 2025 18:15
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant


[8]ページ先頭

©2009-2025 Movatter.jp