You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🛠 Breadcrumb separators are unified into li elements. #40887@heiyu4585
🛠 Tooltip support auto arrow position & adjust position if possible. destroyTooltipOnHide.keepParent is deprecated since it will be always auto destroy unnecessary container now. #40632
🛠 Rename preset colors in token, .e.g blue-1 to blue1, and deprecate tokens before. #41071
A new setting is now supported: dedupe-peer-dependents.
When this setting is set to true, packages with peer dependencies will be deduplicated after peers resolution.
For instance, let's say we have a workspace with two projects and both of them have webpack in their dependencies. webpack has esbuild in its optional peer dependencies, and one of the projects has esbuild in its dependencies. In this case, pnpm will link two instances of webpack to the node_modules/.pnpm directory: one with esbuild and another one without it:
This makes sense because webpack is used in two projects, and one of the projects doesn't have esbuild, so the two projects cannot share the same instance of webpack. However, this is not what most developers expect, especially since in a hoisted node_modules, there would only be one instance of webpack. Therefore, you may now use the dedupe-peer-dependents setting to deduplicate webpack when it has no conflicting peer dependencies (explanation at the end). In this case, if we set dedupe-peer-dependents to true, both projects will use the same webpack instance, which is the one that has esbuild resolved:
In this case, we cannot dedupe webpack as webpack has react in its peer dependencies and react is resolved from two different versions in the context of the two projects.
Patch Changes
The configuration added by pnpm setup should check if the pnpm home directory is already in the PATH before adding to the PATH.
Before this change, this code was added to the shell:
Add skipped status in exec report summary when script is missing #6139.
pnpm env -g should fail with a meaningful error message if pnpm cannot find the pnpm home directory, which is the directory into which Node.js is installed.
Should not throw an error when local dependency use file protocol #6115.
Fix the incorrect error block when subproject has been patched #6183
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
❗ Current head fc99667 differs from pull request most recent head 2867ae0. Consider uploading reports for the commit 2867ae0 to get more accurate results
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
4 times, most recently
from
This PR contains the following updates:
4.14.3->4.15.05.6.12->5.6.135.6.12->5.6.135.6.12->5.6.135.6.12->5.6.135.6.12->5.6.135.6.12->5.6.1313.2.1->13.2.318.14.2->18.14.65.53.0->5.54.05.53.0->5.54.05.2.2->5.3.04.13.0->4.14.010.6.0->10.6.113.2.1->13.2.32.0.20->2.0.217.28.0->7.29.04.1.2->4.3.05.3.6->5.3.81.8.2->1.8.33.20.6->3.21.2Release Notes
algolia/algoliasearch-client-javascript
v4.15.0Compare Source
mikro-orm/mikro-orm
v5.6.13Compare Source
Bug Fixes
vercel/next.js
v13.2.3Compare Source
Core Changes
Credits
Huge thanks to @jridgewell, @DuCanhGH, @wyattjoh, and @hanneslund for helping!
v13.2.2Compare Source
Core Changes
nextwhentypedRoutes: true: #46332server-onlyinside pages/api: #46328imagesprop: #46326server-onlyinside pages/api": #46388readFile+replaceAll, hid utils types, fixed duplication in typeRoute, fixed route groups on Windows: #46378Documentation Changes
next/fontupdates: #46159Example Changes
Misc Changes
next-image-to-legacy-image(#46460Credits
Huge thanks to @balazsorban44, @delbaoliveira, @SukkaW, @ijjk, @hanneslund, @JanKaifer, @GitRowin, @shuding, @styfle, @mjunix, @kwonoj, @thiskevinwang, @DuCanhGH, @SethFalco, @yun-jay, @harrytothemoon, @timneutkens, @huozhi, @thomasballinger, @aretrace, @JesseKoldewijn, @feedthejim, @serkanbektas, @teobler, and @vadzim for helping!
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v5.54.0Compare Source
Features
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v5.54.0Compare Source
Note: Version bump only for package @typescript-eslint/parser
ant-design/ant-design
v5.3.0Compare Source
arrow.pointAtCenterand deprecatearrow.arrowPointAtCenter. #40989 @MadCccsize. #40903 @kiner-tangzIndex. #40982 @kiner-tangonHeaderCellsupport customizecolSpanandrowSpan. #40885onChangecallback. #40857 @kiner-tangstyleprops. #40708 @li-jia-nanmessageandnotificationoptions. #40458 @luo3houseuseConfighook to getsizeanddisabledin context. #40215 @xliezitemsprop. #40543 @heiyu4585lielements. #40887 @heiyu4585destroyTooltipOnHide.keepParentis deprecated since it will be always auto destroy unnecessary container now. #40632blue-1toblue1, and deprecate tokens before. #41071colorTextin style. #41047 @Yuiai01transform: scalestyle. #41013rowScopestyle for Table. #40304 @Yuiai01lineWidthFocusforoutline-widthof focused component. #40840 @MadCccarrowby default when multiple. #41028Form.Item.useStatusproblem with sever-side-rendering. #40977 @AndyBoatReact does not recognize thesuffixClsprop on a DOM elementwarning. #40969fallbackwhen used in ssr. #40660vi_VNadding Vietnamese translation for Form component validation. #40992 @lamvananhrtlmode. #40990 @li-jia-nanarrow.pointAtCenter， 废弃arrow.arrowPointAtCenter。#40989 @MadCccsize。#40903 @kiner-tangzIndex。#40982 @kiner-tangonHeaderCell支持自定义colSpan和rowSpan。#40885onChange回调。#40857 @kiner-tangstyle。#40708 @li-jia-nanmessage、notification的选项。#40458 @luo3houseuseConfig以获取上下文中的size和disabled。#40215 @xliezitems数据驱动。#40543 @heiyu4585li元素。#40887 @heiyu4585destroyTooltipOnHide.keepParent，现在总是会自动销毁不需要的容器。#40632blue-1变为blue1，废弃原有的 token。#41071colorText优化样式。#41047 @Yuiai01transform: scale样式时的对齐问题。#41013rowScope的样式。#40304 @Yuiai01outline提供新的 AliasTokenlineWidthFocus。#40840 @MadCccForm.Item.useStatus导致的服务端渲染问题。#40977 @AndyBoatReact does not recognize thesuffixClsprop on a DOM element的问题。#40969fallback在 ssr 下失效的问题。#40660vi_VN语言包。#40992 @lamvananhrtl模式的问题。#40990 @li-jia-nanv5.2.3Compare Source
percentandsuccess.percentat the same time forProgress, the progress text does not change aspercentchanges. #40922onOkevent could be triggered twice when close. #40719 @Rafael-MartinsuseLocalemethod and exposedlocaleCodeto the public. #40884 @li-jia-nanuseLocaleand removed the LocaleReceiver component. #40870 @li-jia-nangetPopupContainerproperty injected by ConfigProvider did not work. #40871 @RedJuedata-_andaria-_attributes. #40859 @goveospantoli. #40867 @heiyu4585Layout.colorBgHeadernot work when single use Layout.Header directly. #40933outlineto the default4px.#40839 @MadCccclassName. #40835 @Yuiai01onOk可能触发两次的问题。#40719 @Rafael-MartinsuseLocale方法，对外暴露localeCode。#40884 @li-jia-nanuseLocale替换 LocaleReceiver 组件，并删除 LocaleReceiver 组件。#40870 @li-jia-nangetPopupContainer属性 不生效的问题。#40871 @RedJuedata-*和aria-*等属性的问题。#40859 @goveospan改为li。#40867 @heiyu4585outline为默认4px。#40839 @MadCccLayout.colorBgHeadertoken 配置不生效的问题。#40933className错误。#40835 @Yuiai01fastify/fastify
v4.14.0Compare Source
What's Changed
New Contributors
Full Changelog: fastify/fastify@v4.13.0...v4.14.0
harttle/liquidjs
v10.6.1Compare Source
Bug Fixes
remy/nodemon
v2.0.21Compare Source
Bug Fixes
pnpm/pnpm
v7.29.0Compare Source
Minor Changes
A new setting is now supported:
dedupe-peer-dependents.When this setting is set to
true, packages with peer dependencies will be deduplicated after peers resolution.For instance, let's say we have a workspace with two projects and both of them have
webpackin their dependencies.webpackhasesbuildin its optional peer dependencies, and one of the projects hasesbuildin its dependencies. In this case, pnpm will link two instances ofwebpackto thenode_modules/.pnpmdirectory: one withesbuildand another one without it:This makes sense because
webpackis used in two projects, and one of the projects doesn't haveesbuild, so the two projects cannot share the same instance ofwebpack. However, this is not what most developers expect, especially since in a hoistednode_modules, there would only be one instance ofwebpack. Therefore, you may now use thededupe-peer-dependentssetting to deduplicatewebpackwhen it has no conflicting peer dependencies (explanation at the end). In this case, if we setdedupe-peer-dependentstotrue, both projects will use the samewebpackinstance, which is the one that hasesbuildresolved:What are conflicting peer dependencies? By conflicting peer dependencies we mean a scenario like the following one:
In this case, we cannot dedupe
webpackaswebpackhasreactin its peer dependencies andreactis resolved from two different versions in the context of the two projects.Patch Changes
The configuration added by
pnpm setupshould check if the pnpm home directory is already in the PATH before adding to the PATH.Before this change, this code was added to the shell:
Now this will be added:
Add
skippedstatus in exec report summary when script is missing #6139.pnpm env -gshould fail with a meaningful error message if pnpm cannot find the pnpm home directory, which is the directory into which Node.js is installed.Should not throw an error when local dependency use file protocol #6115.
Fix the incorrect error block when subproject has been patched #6183
Our Gold Sponsors
Our Silver Sponsors
isaacs/rimraf
v4.3.0Compare Source
v4.2.0Compare Source
v4.1.4Compare Source
v4.1.3Compare Source
styled-components/styled-components
v5.3.8Compare Source
What's Changed
fix(constants): rework process env guard
Full Changelog: styled-components/styled-components@v5.3.7-fixed...v5.3.8
v5.3.7Compare Source
vercel/turbo
v1.8.3: Turborepo v1.8.3Compare Source
What's Changed
Changelog
Configuration
📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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.
This PR has been generated by Mend Renovate. View repository job log here.