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

Merged
merged 1 commit into from
Apr 5, 2024
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 5, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@ant-design/cssinjs ^1.18.5 -> ^1.19.1 age adoption passing confidence
@octokit/rest ^20.0.2 -> ^20.1.0 age adoption passing confidence
@types/node (source) ^20.12.2 -> ^20.12.4 age adoption passing confidence
@types/react (source) ^18.2.73 -> ^18.2.74 age adoption passing confidence
@types/react-dom (source) ^18.2.23 -> ^18.2.24 age adoption passing confidence
antd (source) ^5.16.0 -> ^5.16.1 age adoption passing confidence
cypress (source) ^13.7.1 -> ^13.7.2 age adoption passing confidence
framer-motion ^11.0.24 -> ^11.0.25 age adoption passing confidence
pnpm (source) 8.15.5 -> 8.15.6 age adoption passing confidence
postcss-preset-env (source) ^9.5.3 -> ^9.5.4 age adoption passing confidence
typescript (source) ^5.4.3 -> ^5.4.4 age adoption passing confidence

Release Notes

ant-design/cssinjs (@​ant-design/cssinjs)

v1.19.1

Compare Source

v1.19.0

Compare Source

octokit/rest.js (@​octokit/rest)

v20.1.0

Compare Source

Features
ant-design/ant-design (antd)

v5.16.1

Compare Source

  • 🛠 Adjust Typography ellipsis logic to use CSS ellipsis in SSR to enhance user experience. #​48205
  • 🐞 Fix FloatButton config tooltip and badge at same time will make badge customize background not working. #​48198 @​LonelySnowman

  • 🛠 调整 Typography 的 ellipsis 使其在 SSR 阶段使用 CSS 省略以优化用户体验。#​48205
  • 🐞 修复 FloatButton 中同时配置 tooltipbadge 时, badge 的自定义背景色会失效的问题。#​48198 @​LonelySnowman
cypress-io/cypress (cypress)

v13.7.2

Compare Source

Changelog: https://docs.cypress.io/guides/references/changelog#13-7-2

framer/motion (framer-motion)

v11.0.25

Compare Source

Fixed
  • Ensuring motion(Fragment) nodes are skipped from layout projection.
pnpm/pnpm (pnpm)

v8.15.6

Compare Source

Patch Changes

  • The exit code of the child process should be preserved on pnpm run #​7817.
  • When sorting packages in a workspace, take into account workspace dependencies specified as peerDependencies #​7813.
  • Add --ignore-scripts argument to prune command #​7836.

Platinum Sponsors

Gold Sponsors

Silver Sponsors

csstools/postcss-plugins (postcss-preset-env)

v9.5.4

Compare Source

April 2, 2024

Microsoft/TypeScript (typescript)

v5.4.4: TypeScript 5.4.4

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, check this box

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 Apr 5, 2024
Copy link

vercel bot commented Apr 5, 2024

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

Name Status Preview Comments Updated (UTC)
blog ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 5, 2024 5:36pm

Copy link
Contributor

github-actions bot commented Apr 5, 2024

Lighthouse Report

https://blog-e5im6wndo-sabertazs-projects.vercel.app/

🚀 Vercel preview deployment
Lighthouse report

Category Score
🟢 performance 90
🟢 accessibility 100
🟡 best-practices 78
🟢 seo 100
🟢 pwa 100

https://blog-e5im6wndo-sabertazs-projects.vercel.app/posts

🚀 Vercel preview deployment
Lighthouse report

Category Score
🟡 performance 77
🟢 accessibility 94
🟡 best-practices 78
🟢 seo 100
🟢 pwa 100

https://blog-e5im6wndo-sabertazs-projects.vercel.app/tags

🚀 Vercel preview deployment
Lighthouse report

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

https://blog-e5im6wndo-sabertazs-projects.vercel.app/books

🚀 Vercel preview deployment
Lighthouse report

Category Score
🟢 performance 100
🟢 accessibility 94
🟡 best-practices 78
🟢 seo 100
🟢 pwa 100

https://blog-e5im6wndo-sabertazs-projects.vercel.app/about

🚀 Vercel preview deployment
Lighthouse report

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

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


Quantification details

Label      : Extra Large
Size       : +251 -251
Percentile : 83.4%

Total files changed: 2

Change summary by file extension:
.json : +11 -11
.yaml : +240 -240

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.

Copy link

codecov bot commented Apr 5, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.43%. Comparing base (d00ecc7) to head (a3e3a64).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1240   +/-   ##
=======================================
  Coverage   98.43%   98.43%           
=======================================
  Files         175      175           
  Lines         830      830           
  Branches       80       81    +1     
=======================================
  Hits          817      817           
+ Misses         12       10    -2     
- Partials        1        3    +2     

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

@sabertazimi sabertazimi merged commit 531a071 into main Apr 5, 2024
15 checks passed
@sabertazimi sabertazimi deleted the renovate/dependencies branch April 5, 2024 18:11
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 Large
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant