graphql-tools

graphql-tools copied to clipboard

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
chalk	^4.1.0 -> ^5.0.0
chalk	4.1.2 -> 5.1.2

---

Configuration

📅 Schedule: Branch creation - "after 10pm,before 6:00am" in timezone Europe/Warsaw, Automerge - At any time (no schedule defined).

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

♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

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

---

• [ ] If you want to rebase/retry this PR, click this checkbox. ⚠ Warning: custom changes will be lost.

---

This PR has been generated by Mend Renovate. View repository job log here.

🦋 Changeset detected

Latest commit: 95767637b03a8c284ce02d99ed9626e3d6c693c4

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@graphql-tools/prisma-loader	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
graphql-tools	❌ Failed (Inspect)		Sep 27, 2022 at 0:38AM (UTC)

❌ Benchmark Failed

Performance regression detected: it seems like your Pull Request adds some extra latency to Schema Stitching

If the performance regression is expected, please increase the failing threshold.

     ✓ no_errors
     ✓ expected_result

     checks.........................: 100.00% ✓ 196      ✗ 0  
     data_received..................: 23 MB   2.3 MB/s
     data_sent......................: 84 kB   8.3 kB/s
     http_req_blocked...............: avg=10.92µs  min=2.8µs    med=3.8µs    max=688.96µs p(90)=4.56µs   p(95)=5.01µs  
     http_req_connecting............: avg=6.37µs   min=0s       med=0s       max=624.65µs p(90)=0s       p(95)=0s      
   ✗ http_req_duration..............: avg=96.19ms  min=80.75ms  med=91.6ms   max=204.21ms p(90)=104.19ms p(95)=135.3ms 
       { expected_response:true }...: avg=96.19ms  min=80.75ms  med=91.6ms   max=204.21ms p(90)=104.19ms p(95)=135.3ms 
     http_req_failed................: 0.00%   ✓ 0        ✗ 98 
     http_req_receiving.............: avg=197.75µs min=145.11µs med=178.81µs max=731.76µs p(90)=225.55µs p(95)=303.81µs
     http_req_sending...............: avg=97.12µs  min=21.7µs   med=30.4µs   max=2.39ms   p(90)=49.94µs  p(95)=174.06µs
     http_req_tls_handshaking.......: avg=0s       min=0s       med=0s       max=0s       p(90)=0s       p(95)=0s      
     http_req_waiting...............: avg=95.9ms   min=80.55ms  med=91.37ms  max=203.83ms p(90)=102.97ms p(95)=134.99ms
     http_reqs......................: 98      9.702657/s
     iteration_duration.............: avg=103.02ms min=87.97ms  med=98.18ms  max=210.61ms p(90)=110.34ms p(95)=141.62ms
     iterations.....................: 98      9.702657/s
     vus............................: 1       min=1      max=1
     vus_max........................: 1       min=1      max=1

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 5.x releases. But if you manually upgrade to 5.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.