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) #887

Merged
merged 1 commit into from
Jun 4, 2022
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 3, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@codesandbox/sandpack-react ^1.0.4 -> ^1.1.1 age adoption passing confidence
@types/node ^16.11.36 -> ^16.11.38 age adoption passing confidence
@types/react ^18.0.9 -> ^18.0.11 age adoption passing confidence
antd (source) ^4.20.6 -> ^4.20.7 age adoption passing confidence
eslint (source) ^8.16.0 -> ^8.17.0 age adoption passing confidence
framer-motion ^6.3.4 -> ^6.3.10 age adoption passing confidence
postcss-preset-env ^7.6.0 -> ^7.7.1 age adoption passing confidence
ts-jest (source) ^28.0.3 -> ^28.0.4 age adoption passing confidence
typescript (source) ^4.7.2 -> ^4.7.3 age adoption passing confidence

Release Notes

codesandbox/sandpack

v1.1.1

Compare Source

Bug Fixes
  • showOpenInCodeSandbox: pass prop to loading component (#​486) (ba81506)

v1.1.0

Compare Source

Features

1.0.4 (2022-05-27)

Bug Fixes

1.0.3 (2022-05-27)

Bug Fixes

1.0.2 (2022-05-26)

Bug Fixes

1.0.1 (2022-05-25)

Bug Fixes
ant-design/ant-design

v4.20.7

Compare Source

  • 🐞 Fix Drawer form instance lost bug when opened. #​35706 @​crazyair
  • 🐞 Fix Segmented options invalid space between icon and text when using the icon prop. #​35701
  • 💄 Optimize Popover arrow style. #​35717
  • TypeScript
    • 🤖 Fix Card type hints problem. #​35753

  • 🐞 修复 Drawer 打开时 form 实例为 null 的问题。#​35706 @​crazyair
  • 🐞 修复 Segmented 组件中选项使用 icon 属性时图标与文字之间的间距失效问题。#​35701
  • 💄 优化 Popover 的箭头效果。#​35717
  • TypeScript
    • 🤖 修复 Card 组件的类型提示。#​35753
eslint/eslint

v8.17.0

Compare Source

Features

  • 55319e1 feat: fix indent bug with semicolon-first style (#​15951) (Milos Djermanovic)
  • f6d7920 feat: add allowNamedExports option to no-use-before-define (#​15953) (Milos Djermanovic)

Bug Fixes

Documentation

Chores

framer/motion

v6.3.10

Compare Source

Fixed
  • Fixing version mismatch warning.

v6.3.9

Compare Source

Fixed
  • Providing path to types via package.json's exports field to fix types in TypeScript 4.7.
  • Safer process.env.NODE_ENV check.

v6.3.8

Compare Source

Fixed
  • Restore scroll position after measuring height when doing unit conversion animation.

v6.3.7

Compare Source

Fixed
  • Will display a warning if different versions of Framer Motion are mixed.

v6.3.6

Compare Source

Fixed
  • All events are now passive unless a user provides an explicit event listener.

v6.3.5

Compare Source

Fixed
  • Added initial prop to Framer Motion 3D types.
csstools/postcss-plugins

v7.7.1

Compare Source

  • Updated postcss-selector-not to 6.0.0 (major)
  • Updated @csstools/postcss-trigonometric-functions to 1.0.1 (patch)
  • Updated postcss-attribute-case-insensitive to 5.0.1 (patch)
  • Updated postcss-custom-media to 8.0.1 (patch)
  • Updated postcss-custom-selectors to 6.0.2 (patch)
  • Updated cssdb to 6.6.3 (patch)

v7.7.0

Compare Source

  • Added @csstools/postcss-trigonometric-functions
    Check the plugin README for usage details.
  • Updated @csstools/postcss-cascade-layers to 1.0.2 (patch)
  • Updated postcss-color-functional-notation to 4.2.3 (patch)
  • Updated postcss-nesting to 10.1.7 (patch)
kulshekhar/ts-jest

v28.0.4

Compare Source

Bug Fixes
Microsoft/TypeScript

v4.7.3

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:


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 Jun 3, 2022
@vercel
Copy link

vercel bot commented Jun 3, 2022

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

Name Status Preview Updated
blog ✅ Ready (Inspect) Visit Preview Jun 4, 2022 at 3:55AM (UTC)

@github-actions
Copy link
Contributor

github-actions bot commented Jun 3, 2022

Lighthouse Report

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

🚀 Vercel preview deployment
Lighthouse report

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

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

🚀 Vercel preview deployment
Lighthouse report

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

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

🚀 Vercel preview deployment
Lighthouse report

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

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

🚀 Vercel preview deployment
Lighthouse report

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

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

🚀 Vercel preview deployment
Lighthouse report

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

@codecov
Copy link

codecov bot commented Jun 3, 2022

Codecov Report

Merging #887 (943ce84) into main (0cc8318) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #887   +/-   ##
=======================================
  Coverage   99.40%   99.40%           
=======================================
  Files         175      175           
  Lines        1012     1012           
  Branches       86       86           
=======================================
  Hits         1006     1006           
  Misses          5        5           
  Partials        1        1           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0cc8318...943ce84. Read the comment docs.

@pull-request-quantifier-deprecated

This PR has 18 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       : +9 -9
Percentile : 7.2%

Total files changed: 2

Change summary by file extension:
.json : +9 -9
.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 detetcted.
  • 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.

@renovate renovate bot merged commit 7c63f0a into main Jun 4, 2022
@renovate renovate bot deleted the renovate/dependencies branch June 4, 2022 05:52
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.

1 participant