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(deps): update nextjs monorepo to v15.1.7 #2041

Merged
merged 1 commit into from
Feb 11, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 11, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
eslint-config-next (source) 15.1.6 -> 15.1.7 age adoption passing confidence
next (source) 15.1.6 -> 15.1.7 age adoption passing confidence

Release Notes

vercel/next.js (eslint-config-next)

v15.1.7

Compare Source

vercel/next.js (next)

v15.1.7

Compare Source


Configuration

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

🚦 Automerge: Enabled.

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

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


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

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Feb 11, 2025
Copy link

coderabbitai bot commented Feb 11, 2025

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@benchmarks/node-fetch results (consumeBody)

   ✓ active_handles.................: avg=140.30555 min=22     med=140     max=183     p(90)=162     p(95)=166    
     data_received..................: 20 MB  673 kB/s
     data_sent......................: 13 MB  431 kB/s
     http_req_blocked...............: avg=3.38µs    min=671ns  med=1.26µs  max=5.21ms  p(90)=2.03µs  p(95)=2.31µs 
     http_req_connecting............: avg=1.55µs    min=0s     med=0s      max=5.18ms  p(90)=0s      p(95)=0s     
     http_req_duration..............: avg=22.68ms   min=3.37ms med=22.11ms max=1.17s   p(90)=28.41ms p(95)=29.82ms
       { expected_response:true }...: avg=22.68ms   min=3.37ms med=22.11ms max=1.17s   p(90)=28.41ms p(95)=29.82ms
     http_req_failed................: 0.00%  ✓ 0           ✗ 131887
     http_req_receiving.............: avg=33.15µs   min=8.98µs med=23.44µs max=14.88ms p(90)=37.19µs p(95)=43.96µs
     http_req_sending...............: avg=11.15µs   min=3.23µs med=5.8µs   max=33.88ms p(90)=9.56µs  p(95)=13.87µs
     http_req_tls_handshaking.......: avg=0s        min=0s     med=0s      max=0s      p(90)=0s      p(95)=0s     
     http_req_waiting...............: avg=22.63ms   min=3.34ms med=22.07ms max=1.17s   p(90)=28.38ms p(95)=29.76ms
     http_reqs......................: 131887 4395.755418/s
     iteration_duration.............: avg=45.45ms   min=16.1ms med=43.86ms max=1.2s    p(90)=49.22ms p(95)=54.85ms
     iterations.....................: 65904  2196.561185/s
     vus............................: 100    min=100       max=100 
     vus_max........................: 100    min=100       max=100 

Copy link
Contributor

@benchmarks/node-fetch results (noConsumeBody)

   ✓ active_handles.................: avg=140.497204 min=34      med=142     max=177     p(90)=161     p(95)=164    
     data_received..................: 21 MB  702 kB/s
     data_sent......................: 14 MB  455 kB/s
     http_req_blocked...............: avg=3.43µs     min=681ns   med=1.31µs  max=5.29ms  p(90)=2.01µs  p(95)=2.3µs  
     http_req_connecting............: avg=1.38µs     min=0s      med=0s      max=5.19ms  p(90)=0s      p(95)=0s     
     http_req_duration..............: avg=21.71ms    min=2.64ms  med=21.16ms max=1.12s   p(90)=27.37ms p(95)=28.87ms
       { expected_response:true }...: avg=21.71ms    min=2.64ms  med=21.16ms max=1.12s   p(90)=27.37ms p(95)=28.87ms
     http_req_failed................: 0.00%  ✓ 0           ✗ 137725
     http_req_receiving.............: avg=32.26µs    min=9.45µs  med=22.58µs max=22.35ms p(90)=36.86µs p(95)=43.81µs
     http_req_sending...............: avg=10.79µs    min=3.24µs  med=5.89µs  max=24.26ms p(90)=9.46µs  p(95)=13.9µs 
     http_req_tls_handshaking.......: avg=0s         min=0s      med=0s      max=0s      p(90)=0s      p(95)=0s     
     http_req_waiting...............: avg=21.67ms    min=2.48ms  med=21.12ms max=1.12s   p(90)=27.33ms p(95)=28.81ms
     http_reqs......................: 137725 4590.32441/s
     iteration_duration.............: avg=43.53ms    min=17.52ms med=41.98ms max=1.15s   p(90)=47.47ms p(95)=53.39ms
     iterations.....................: 68849  2294.712255/s
     vus............................: 100    min=100       max=100 
     vus_max........................: 100    min=100       max=100 

Copy link
Contributor

@benchmarks/server results (native)

     ✓ no-errors
     ✓ expected-result

   ✓ checks.........................: 100.00% ✓ 209440      ✗ 0     
     data_received..................: 21 MB   702 kB/s
     data_sent......................: 8.4 MB  279 kB/s
     http_req_blocked...............: avg=1.41µs   min=921ns    med=1.18µs   max=553.26µs p(90)=1.9µs    p(95)=2.08µs  
     http_req_connecting............: avg=3ns      min=0s       med=0s       max=394.29µs p(90)=0s       p(95)=0s      
     http_req_duration..............: avg=223.77µs min=170.12µs med=212.61µs max=7.35ms   p(90)=240.89µs p(95)=251.89µs
       { expected_response:true }...: avg=223.77µs min=170.12µs med=212.61µs max=7.35ms   p(90)=240.89µs p(95)=251.89µs
     http_req_failed................: 0.00%   ✓ 0           ✗ 104720
     http_req_receiving.............: avg=25.11µs  min=13.77µs  med=23.24µs  max=2.43ms   p(90)=30.5µs   p(95)=33.25µs 
     http_req_sending...............: avg=6.33µs   min=4.12µs   med=5.46µs   max=319.58µs p(90)=8.12µs   p(95)=8.82µs  
     http_req_tls_handshaking.......: avg=0s       min=0s       med=0s       max=0s       p(90)=0s       p(95)=0s      
     http_req_waiting...............: avg=192.32µs min=145.55µs med=181.13µs max=7.3ms    p(90)=206.25µs p(95)=216.34µs
     http_reqs......................: 104720  3490.316046/s
     iteration_duration.............: avg=282.03µs min=214.8µs  med=270.32µs max=7.44ms   p(90)=301.82µs p(95)=314.64µs
     iterations.....................: 104720  3490.316046/s
     vus............................: 0       min=0         max=1   
     vus_max........................: 1       min=1         max=1   

Copy link
Contributor

@benchmarks/server results (undici)

     ✓ no-errors
     ✓ expected-result

   ✓ checks.........................: 100.00% ✓ 192736      ✗ 0    
     data_received..................: 19 MB   646 kB/s
     data_sent......................: 7.7 MB  257 kB/s
     http_req_blocked...............: avg=1.46µs   min=912ns    med=1.22µs   max=286.76µs p(90)=1.95µs   p(95)=2.16µs  
     http_req_connecting............: avg=1ns      min=0s       med=0s       max=131.05µs p(90)=0s       p(95)=0s      
     http_req_duration..............: avg=246.56µs min=188.97µs med=233.24µs max=33.99ms  p(90)=262.83µs p(95)=274.92µs
       { expected_response:true }...: avg=246.56µs min=188.97µs med=233.24µs max=33.99ms  p(90)=262.83µs p(95)=274.92µs
     http_req_failed................: 0.00%   ✓ 0           ✗ 96368
     http_req_receiving.............: avg=25.73µs  min=13.73µs  med=23.92µs  max=1.83ms   p(90)=31.41µs  p(95)=34.5µs  
     http_req_sending...............: avg=6.67µs   min=4.28µs   med=5.91µs   max=1.18ms   p(90)=8.42µs   p(95)=9.31µs  
     http_req_tls_handshaking.......: avg=0s       min=0s       med=0s       max=0s       p(90)=0s       p(95)=0s      
     http_req_waiting...............: avg=214.16µs min=164.63µs med=200.8µs  max=33.91ms  p(90)=227.26µs p(95)=237.99µs
     http_reqs......................: 96368   3212.077979/s
     iteration_duration.............: avg=306.76µs min=232.84µs med=292.5µs  max=34.14ms  p(90)=326.08µs p(95)=340.64µs
     iterations.....................: 96368   3212.077979/s
     vus............................: 1       min=1         max=1  
     vus_max........................: 1       min=1         max=1  

Copy link
Contributor

@benchmarks/server results (ponyfill)

     ✓ no-errors
     ✓ expected-result

   ✓ checks.........................: 100.00% ✓ 296172      ✗ 0     
     data_received..................: 29 MB   972 kB/s
     data_sent......................: 12 MB   395 kB/s
     http_req_blocked...............: avg=1.37µs   min=891ns    med=1.18µs   max=203.09µs p(90)=1.83µs   p(95)=1.98µs  
     http_req_connecting............: avg=0ns      min=0s       med=0s       max=142.47µs p(90)=0s       p(95)=0s      
     http_req_duration..............: avg=139.94µs min=96.62µs  med=135.3µs  max=5.9ms    p(90)=157.37µs p(95)=164.13µs
       { expected_response:true }...: avg=139.94µs min=96.62µs  med=135.3µs  max=5.9ms    p(90)=157.37µs p(95)=164.13µs
     http_req_failed................: 0.00%   ✓ 0           ✗ 148086
     http_req_receiving.............: avg=24.51µs  min=11.81µs  med=22.85µs  max=2.55ms   p(90)=30.4µs   p(95)=33.04µs 
     http_req_sending...............: avg=6.34µs   min=4.13µs   med=5.49µs   max=285.88µs p(90)=8.13µs   p(95)=8.79µs  
     http_req_tls_handshaking.......: avg=0s       min=0s       med=0s       max=0s       p(90)=0s       p(95)=0s      
     http_req_waiting...............: avg=109.07µs min=70.23µs  med=104.26µs max=5.79ms   p(90)=123.05µs p(95)=128.55µs
     http_reqs......................: 148086  4936.020067/s
     iteration_duration.............: avg=198.03µs min=141.11µs med=192.79µs max=6.3ms    p(90)=217.86µs p(95)=226.6µs 
     iterations.....................: 148086  4936.020067/s
     vus............................: 1       min=1         max=1   
     vus_max........................: 1       min=1         max=1   

@renovate renovate bot merged commit a2a0295 into master Feb 11, 2025
25 checks passed
@renovate renovate bot deleted the renovate/nextjs-monorepo branch February 11, 2025 13:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants