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 dependencies (non-major) #962

Merged
merged 1 commit into from
Aug 26, 2022
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 26, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@codesandbox/sandpack-react ^1.5.1 -> ^1.5.5 age adoption passing confidence
@types/jest ^28.1.7 -> ^28.1.8 age adoption passing confidence
antd (source) ^4.22.7 -> ^4.22.8 age adoption passing confidence
framer-motion ^7.2.0 -> ^7.2.1 age adoption passing confidence
rehype-external-links ^2.0.0 -> ^2.0.1 age adoption passing confidence
typescript (source) ^4.7.4 -> ^4.8.2 age adoption passing confidence
yarn 3.2.2 -> 3.2.3 age adoption passing confidence

Release Notes

codesandbox/sandpack

v1.5.5

Compare Source

Bug Fixes
  • UnstyledOpenInCodeSandboxButton: set visibility to hidden (#​560) (653cf0e)

v1.5.4

Compare Source

Bug Fixes
  • client: do not set default credentials for custom npm requests (4ce7be9)

v1.5.3

Compare Source

Bug Fixes
  • client: custom registry should include the credentials only for csb urls (#​555) (de1e424)

v1.5.2

Compare Source

Bug Fixes
  • custom registry: cors issue and make the types more strict (#​554) (dca96ec)
ant-design/ant-design

v4.22.8

Compare Source


framer/motion

v7.2.1

Compare Source

Added
  • Various filesize reductions.
rehypejs/rehype-external-links

v2.0.1

Compare Source

  • 3c6b438 Fix to treat protocol-relative URLs as external

Full Changelog: rehypejs/rehype-external-links@2.0.0...2.0.1

Microsoft/TypeScript

v4.8.2

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

yarnpkg/berry

v3.2.3

Compare Source


Configuration

📅 Schedule: Branch creation - "every weekend" in timezone Asia/Shanghai, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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

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


  • If you want to rebase/retry this PR, click this checkbox.

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

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Aug 26, 2022
@vercel
Copy link

vercel bot commented Aug 26, 2022

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

Name Status Preview Updated
blog ✅ Ready (Inspect) Visit Preview Aug 26, 2022 at 6:53PM (UTC)

@pull-request-quantifier-deprecated

This PR has 16 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!


Quantification details

Label      : Extra Small
Size       : +8 -8
Percentile : 6.4%

Total files changed: 3

Change summary by file extension:
.yml : +1 -1
.json : +7 -7
.lock : +0 -0

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

  • Fast and predictable releases to production:
    • Optimal size changes are more likely to be reviewed faster with fewer
      iterations.
    • Similarity in low PR complexity drives similar review times.
  • Review quality is likely higher as complexity is lower:
    • Bugs are more likely to be detected.
    • Code inconsistencies are more likely to be detected.
  • Knowledge sharing is improved within the participants:
    • Small portions can be assimilated better.
  • Better engineering practices are exercised:
    • Solving big problems by dividing them in well contained, smaller problems.
    • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

  • Use the PullRequestQuantifier to quantify your PR accurately
    • Create a context profile for your repo using the context generator
    • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
    • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
    • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
  • Change your engineering behaviors
    • For PRs that fall outside of the desired spectrum, review the details and check if:
      • Your PR could be split in smaller, self-contained PRs instead
      • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

  • One line was added: +1 -0
  • One line was deleted: +0 -1
  • One line was modified: +1 -1 (git diff doesn't know about modified, it will
    interpret that line like one addition plus one deletion)
  • Change percentiles: Change characteristics (addition, deletion, modification)
    of this PR in relation to all other PRs within the repository.


Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

@github-actions
Copy link
Contributor

github-actions bot commented Aug 26, 2022

Lighthouse Report

https://blog-rjdre9kkx-sabertaz.vercel.app/

🚀 Vercel preview deployment
Lighthouse report

Category Score
🟢 performance 97
🟢 accessibility 100
🟢 best-practices 100
🟢 seo 100
🟢 pwa 100

https://blog-rjdre9kkx-sabertaz.vercel.app/posts

🚀 Vercel preview deployment
Lighthouse report

Category Score
🟢 performance 99
🟢 accessibility 100
🟢 best-practices 100
🟢 seo 100
🟢 pwa 100

https://blog-rjdre9kkx-sabertaz.vercel.app/tags

🚀 Vercel preview deployment
Lighthouse report

Category Score
🟢 performance 98
🟢 accessibility 100
🟢 best-practices 100
🟢 seo 100
🟢 pwa 100

https://blog-rjdre9kkx-sabertaz.vercel.app/books

🚀 Vercel preview deployment
Lighthouse report

Category Score
🟢 performance 99
🟢 accessibility 100
🟢 best-practices 100
🟢 seo 100
🟢 pwa 100

https://blog-rjdre9kkx-sabertaz.vercel.app/about

🚀 Vercel preview deployment
Lighthouse report

Category Score
🟢 performance 99
🟢 accessibility 100
🟢 best-practices 100
🟢 seo 100
🟢 pwa 100

@codecov
Copy link

codecov bot commented Aug 26, 2022

Codecov Report

Merging #962 (6787f8c) into main (d6bd9c3) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #962   +/-   ##
=======================================
  Coverage   99.42%   99.42%           
=======================================
  Files         176      176           
  Lines        1039     1039           
  Branches       88       88           
=======================================
  Hits         1033     1033           
  Misses          5        5           
  Partials        1        1           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@renovate renovate bot merged commit 717308c into main Aug 26, 2022
@renovate renovate bot deleted the renovate/dependencies branch August 26, 2022 22:25
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 Extra Small
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants