Skip to content
This repository has been archived by the owner on Jun 19, 2023. It is now read-only.

Update all non-major dependencies #72

Merged
merged 1 commit into from May 11, 2023
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 28, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@emotion/react (source) 11.10.8 -> 11.11.0 age adoption passing confidence
@emotion/styled (source) 11.10.8 -> 11.11.0 age adoption passing confidence
@mui/material (source) 5.12.2 -> 5.13.0 age adoption passing confidence
@typescript-eslint/eslint-plugin 5.59.1 -> 5.59.5 age adoption passing confidence
@typescript-eslint/parser 5.59.1 -> 5.59.5 age adoption passing confidence
@vitejs/plugin-react-swc 3.3.0 -> 3.3.1 age adoption passing confidence
eslint (source) 8.39.0 -> 8.40.0 age adoption passing confidence
eslint-plugin-react-refresh ^0.3.3 -> ^0.4.0 age adoption passing confidence
happy-dom 9.9.2 -> 9.13.1 age adoption passing confidence
react-router-dom 6.10.0 -> 6.11.1 age adoption passing confidence
vite (source) 4.3.3 -> 4.3.5 age adoption passing confidence
vitest ^0.30.0 -> ^0.31.0 age adoption passing confidence

Release Notes

emotion-js/emotion

v11.11.0

Compare Source

Minor Changes
Patch Changes
mui/material-ui

v5.13.0

Compare Source

May 10, 2023

A big thanks to the 18 contributors who made this release possible. Here are some highlights ✨:

  • 🚀 Base UI is now in beta - all planned breaking changes are now complete!
  • 🗺 We have a new project roadmap on GitHub where you can learn about what's coming next.
  • 🐛 Various bug fixes, 📚 documentation and 🧪 testing improvements
@mui/material@5.13.0
@mui/joy@5.0.0-alpha.79
@mui/base@5.0.0-beta.0
Docs
Core

All contributors of this release in alphabetical order: @​akash191095, @​DanailH, @​danilo-leal, @​DerTimonius, @​gerdadesign, @​hbjORbj, @​kriskw1999, @​michaldudak, @​mnajdova, @​oliviertassinari, @​PunitSoniME, @​romgrk, @​sai6855, @​ulrichstark, @​uuxxx, @​wewakekumar, @​ZeeshanTamboli, @​zignis

v5.12.3

Compare Source

May 2, 2023

A big thanks to the 18 contributors who made this release possible. Here are some highlights ✨:

  • all planned breaking changes for Base UI are done. The first beta release should come next week 🎉
  • 🐛 bug fixes and 📚 documentation improvements.
@mui/material@5.12.3
@mui/joy@5.0.0-alpha.78
@mui/base@5.0.0-alpha.128
Breaking changes
  • The component prop is no longer supported because it can be replaced with the slots API. This is how the transformation will look like:

     <Button
    -  component="span"
    +  slots={{ root: "span" }}
     />

    If using TypeScript, the custom component type should be added as a generic on the Button component.

    -<Button
    +<Button<typeof CustomComponent>
       slots={{ root: CustomComponent }}
       customProp="foo"
     />

    There is codemod that you can run in your project to do the transformation:

    npx @&#8203;mui/codemod v5.0.0/base-remove-component-prop <path>

    The full documentation about the codemod can be found here.

    This is the list of PR related to this change:

  • ​[base] Improve API consistency (#​36970) @​michaldudak

    Brought consistency to Base UI components and hooks' parameters and return values:

    1. Whenever a hook needs a ref, it's now called <slot_name>Ref, which matches the get<slot_name>Props in the return value.
    2. All hooks that accept external refs now return merged refs, making combining multiple hooks on one element easier. This was proven necessary in several compound components (like menuItem being both a button and a list item). The type of this value is React.RefCallback as using the more general React.Ref caused variance issues.
    3. Type of accepted refs is standardized to React.Ref<Element>
    4. Naming and typing of the forwarded ref in unstyled components were standardized - it's forwardedRef: React.ForwardedRef (unless a more specific type is needed).
    5. The shape of the definition of unstyled components was standardized - it's React.forwardRef(function Component(props: Props, forwardedRef: React.Ref) { ... });. Specifically, the generic parameters of forwardRef were removed as they are specified in function arguments.
Changes
Docs
Core

All contributors of this release in alphabetical order: @​cherniavskii, @​DavidBoyer11, @​hbjORbj, @​jakub-stastny, @​joserodolfofreitas, @​maxdestors, @​michaldudak, @​mj12albert, @​mnajdova, @​navedqb, @​nicolas-ot, @​oliviertassinari, @​PunitSoniME, @​sai6855, @​samuelsycamore, @​siriwatknp, @​varunmulay22, @​ZeeshanTamboli

typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v5.59.5

Compare Source

Note: Version bump only for package @​typescript-eslint/eslint-plugin

v5.59.2

Compare Source

Note: Version bump only for package @​typescript-eslint/eslint-plugin

typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v5.59.5

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

v5.59.2

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

vitejs/vite-plugin-react-swc

v3.3.1

Compare Source

  • Add type: module to package.json (#​101). Because the library already publish .cjs & .mjs files, the only change is for typing when using the node16 module resolution (fixes #​95)
  • Throw an error when the MDX plugin is after this one (#​100). This is an expected breaking change added in 3.2.0 and this should people that were using both plugins before this version to migrate.
eslint/eslint

v8.40.0

Compare Source

Features

  • 5db7808 feat: improve flat config errors for invalid rule options and severities (#​17140) (Josh Goldberg ✨)
  • f5574dc feat: Add findConfigFile() method to FlatESLint (#​17142) (Nicholas C. Zakas)
  • e52b98b feat: add sourceCode property to the rule context (#​17107) (Nitin Kumar)
  • 1468f5b feat: add physicalFilename property to the rule context (#​17111) (Nitin Kumar)
  • 0df4d4f feat: add cwd to rule context (#​17106) (Nitin Kumar)
  • 52018f2 feat: add filename property to the rule context (#​17108) (Nitin Kumar)
  • 559ff4e feat: add new omitLastInOneLineClassBody option to the semi rule (#​17105) (Nitin Kumar)

Bug Fixes

  • f076e54 fix: Ensure FlatESLint#findConfigFile() doesn't throw. (#​17151) (Nicholas C. Zakas)

Documentation

  • e980bf3 docs: Update README (GitHub Actions Bot)
  • e92a6fc docs: Update README (GitHub Actions Bot)
  • af5fe64 docs: Fix custom rule schema docs (#​17115) (Adam Jones)
  • 4a352a9 docs: explain how to include predefined globals (#​17114) (Marcus Wyatt)
  • 5ea15d9 docs: add mastodon link in readme (#​17110) (唯然)

Chores

ArnaudBarre/eslint-plugin-react-refresh

v0.4.1

Compare Source

  • Ignore export type * (fixes #​12)
  • Support for all-uppercase function wrapped in forwardRef/memo (#​11)

v0.4.0

Compare Source

Add allowConstantExport option (fixes #​8)

This option allow to don't warn when a constant (string, number, boolean, templateLiteral) is exported aside one or more components.

This should be enabled if the fast refresh implementation correctly handles this case (HMR when the constant doesn't change, propagate update to importers when the constant changes). Vite supports it, PR welcome if you notice other integrations works well.

Allow all-uppercase function exports (fixes #​11)

This only works when using direct export. So this pattern doesn't warn anymore:

export const CMS = () => <></>;

But this one will still warn:

const CMS = () => <></>;
export default CMS;
capricorn86/happy-dom

v9.13.1

Compare Source

👷‍♂️ Patch fixes
  • Fix parseCSSRules parsing keyframe error. (#​889)

v9.13.0

Compare Source

🎨 Features
  • Improves performance of Element.querySelectorAll(). The performance was decreased after the implementation of document sorting order, due to the fact that it relied on Object.assign() for each match, which is slower than iterating through all matches in the end. (#​909)

v9.12.0

Compare Source

🎨 Features
  • Adds support for the "of selector" to ":nth-child" and ":nth-last-child" query selectors. (#​905)
👷‍♂️ Patch fixes
  • Fixes bug but where "nth-*" query selectors didn't return the correct elements when prefixing "n" with "-". (#​905)

v9.11.0

Compare Source

🎨 Features
  • Refactors the XML parser, which fixes several issues related to parsing complex HTML (e.g. attributes containing ">"). (#​578)
  • Improves performance of XML parsing significantly. (#​578)

v9.10.9

Compare Source

👷‍♂️ Patch fixes
  • Adds support for Request.formData(). (#​892)

Thank you @​rolandjohann for your contribution!

v9.10.8

Compare Source

👷‍♂️ Patch fixes
  • Fixes an issue where HTMLAnchorElement.toString() returned "HTMLElement.outerHTML", but should return "HTMLAnchorElement.href" according to spec. (#​890)

Thank you @​Schleuse for your contribution!

v9.10.7

Compare Source

👷‍♂️ Patch fixes
  • Fix for parsing CSS comments with asterisks. (#​887)

Thank you for your contribution @​htuomola!

v9.10.6

Compare Source

👷‍♂️ Patch fixes
  • Fixes bug where errors where not handled correctly when performing a synchronous request with XMLHttpRequest. (#​795)
  • Adds support for XMLHttpRequest.response. (#​788)

Thank you @​Mas0nShi for your contribution!

v9.10.5

Compare Source

👷‍♂️ Patch fixes
  • Fixes issue in HTMLCollection and HTMLFormControlsCollection related to id/name of elements colliding with class properties and methods. (#​875)

v9.10.4

Compare Source

👷‍♂️ Patch fixes
  • Fixes issue related to query selection for attributes not using apostrophe for the value. This caused an issue with finding elements by text in Testing Library. (#​883)

v9.10.3

Compare Source

👷‍♂️ Patch fixes
  • Fixes issue where React "onChange" listeners never got executed when triggering a click(). (#​880)
  • Fixes issue where it was not possible to use multiple pseudo query selectors (e.g. "input:not([type]):not([list])"). This solves a problem in Testing Library where it failed to find elements by role "checkbox". (#​880)

v9.10.2

Compare Source

👷‍♂️ Patch fixes
  • Fixes issue related to query selection for attributes with empty value (e.g. '[attr1=""]'). (#​881)

v9.10.1

Compare Source

👷‍♂️ Patch fixes
  • Adds support for using escaped characters to ID:s in query selectors (e.g. "#\\:id"). (#​877)

v9.10.0

Compare Source

🎨 Features
  • Refactors the internal logic of how query selection works to improve performance and make maintenance easier. (#​792)
  • Adds support for adjacent sibling to query selectors (e.g. ".a + .b"). (#​792)
👷‍♂️ Patch fixes
  • Fixes issue where *.querySelectorAll() did not return elements in document order. (#​285)
remix-run/react-router

v6.11.1

Compare Source

Patch Changes
  • Updated dependencies:
    • react-router@6.11.1
    • @remix-run/router@1.6.1

v6.11.0

Compare Source

Minor Changes
  • Enable basename support in useFetcher (#​10336)
    • If you were previously working around this issue by manually prepending the basename then you will need to remove the manually prepended basename from your fetcher calls (fetcher.load('/basename/route') -> fetcher.load('/route'))
Patch Changes
  • Fix inadvertent re-renders when using Component instead of element on a route definition (#​10287)
  • Fail gracefully on <Link to="//"> and other invalid URL values (#​10367)
  • Switched from useSyncExternalStore to useState for internal @remix-run/router router state syncing in <RouterProvider>. We found some subtle bugs where router state updates got propagated before other normal useState updates, which could lead to footguns in useEffect calls. (#​10377, #​10409)
  • Add static prop to StaticRouterProvider's internal Router component (#​10401)
  • When using a RouterProvider, useNavigate/useSubmit/fetcher.submit are now stable across location changes, since we can handle relative routing via the @remix-run/router instance and get rid of our dependence on useLocation(). When using BrowserRouter, these hooks remain unstable across location changes because they still rely on useLocation(). (#​10336)
  • Updated dependencies:
    • react-router@6.11.0
    • @remix-run/router@1.6.0
vitejs/vite

v4.3.5

Compare Source

v4.3.4

Compare Source

vitest-dev/vitest

v0.31.0

Compare Source

   🚨 Breaking Changes
  • Remove browser from allowed pools inside poolMatchGlob config option. Please, use Vitest workspaces for running tests in the browser.

  • Move assertion declarations to expect package  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3294 (cf3af)

    • The change should be minor:
    - declare namespace Vi {
    + declare module 'vitest' {
       interface Assertion<T = any> extends CustomMatchers<T> {}
       interface AsymmetricMatchersContaining extends CustomMatchers {}
    }
   🚀 Features
   🐞 Bug Fixes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.


  • If you want to rebase/retry this PR, check this box

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

@cloudflare-pages
Copy link

cloudflare-pages bot commented Apr 28, 2023

Deploying with  Cloudflare Pages  Cloudflare Pages

Latest commit: 6339d9a
Status: ✅  Deploy successful!
Preview URL: https://249b29c0.showcase-n7k.pages.dev
Branch Preview URL: https://renovate-all-minor-patch.showcase-n7k.pages.dev

View logs

@2na2-p 2na2-p bot enabled auto-merge April 28, 2023 20:49
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 22 times, most recently from 5bb1774 to 8315271 Compare May 6, 2023 15:05
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from eeff45c to 783afba Compare May 11, 2023 10:39
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 783afba to 6339d9a Compare May 11, 2023 19:18
@2na2-p 2na2-p bot merged commit f7a317e into master May 11, 2023
4 checks passed
@2na2-p 2na2-p bot deleted the renovate/all-minor-patch branch May 11, 2023 19:19
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants