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.

Sign up for GitHub

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

Jump to bottom

fix(deps): Update react packages (major) #717

Closed
wants to merge 1 commit into from
Closed

fix(deps): Update react packages (major) #717

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 31, 2022 •
edited

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@storybook/react (source) ^6.5.12 -> ^7.0.0 age adoption passing confidence
@testing-library/react ^11.2.3 -> ^14.0.0 age adoption passing confidence
@types/react (source) ^17.0.0 -> ^18.0.0 age adoption passing confidence
@types/react-dom (source) ^17.0.0 -> ^18.0.0 age adoption passing confidence
react (source) ^17.0.1 -> ^18.0.0 age adoption passing confidence
react-dom (source) ^17.0.1 -> ^18.0.0 age adoption passing confidence
react-router-dom ^5.2.0 -> ^6.0.0 age adoption passing confidence

Release Notes

storybookjs/storybook

v7.0.7

Compare Source

Bug Fixes
  • Core: Pass parameters in SET_INDEX for docs entries #​22154
  • Addon-actions: Fix ESM by upgrading from uuid-browser to uuid #​22037
  • Addon-actions: Fix decorator type #​22175
  • Core: Add new tags to distinguish docs attachment #​22120
  • Core: Restore Docs useParameter using DOCS_PREPARED #​22118
Maintenance
  • CSF: Improve error message for bad default export #​22190
  • CLI: Add addon query-params to list of SB7 incompatible addons #​22095
  • UI: Add remount story shortcut #​21401
Build

v7.0.6

Compare Source

Bug Fixes
  • Core: Fix module guard in non-webpack environments #​22085
Maintenance
  • CLI: Mark qwik as using addon-interactions #​22000
Build
  • Build: Upgrade Playwright to 1.32.3 #​22087

v7.0.5

Compare Source

Bug Fixes
  • Docs: Fix source snippets when parameters.docs.source.type = 'code' #​22048
  • CLI: Mention how to setup a monorepo manually in babelrc automigration #​22052
  • UI: Fix upgrade command in about page #​22056
  • CLI: Fix CLI sandbox command #​21977

v7.0.4

Compare Source

Storybook 7.0 is here! 🎉

7.0 contains hundreds more fixes, features, and tweaks. Browse the changelogs matching 7.0.0-alpha.*, 7.0.0-beta.*, and 7.0.0-rc.* for the full list of changes.

See our Migration guide to upgrade from earlier versions of Storybook.

Bug Fixes
  • CLI: Catch errors thrown on sanity check of SB installs #​22039
Dependency Upgrades
  • Addon-docs: Remove mdx1-csf as optional peer dep #​22038

v7.0.3

Compare Source

Bug Fixes
  • React: Fix default export docgen for React.FC and forwardRef #​22024
  • Viewport: Remove transitions when switching viewports #​21963
  • CLI: Fix JsPackageManager typo #​22006
  • Viewport: Fix the defaultOrientation config option #​21962
  • UI: Fix story data access for broken About page #​21951
  • Angular: Fix components disappearing on docs page on property change #​21944
  • React: Don't show decorators in JSX snippets #​21907
  • Addon-docs: Include decorators by default in source decorators #​21902
  • CLI: Fix npm list command #​21947
  • Core: Revert Emotion :first-child (etc) workarounds #​21213
Maintenance
  • UI: Add remount story shortcut #​21401
  • Telemetry: Add CLI version to context #​21999
  • CLI: Update template code references to 7.0 #​21845
  • Addon-actions: Fix non-included type file #​21922
  • Addon GFM: Fix node-logger dependency #​21938
Dependency Upgrades
  • React-vite: Fix perf regression by pinning vite-plugin-react-docgen-ts #​22013
  • Update @emotion/cache version #​21941

v7.0.2

Compare Source

Storybook 7.0 is here! 🎉

7.0 contains hundreds more fixes, features, and tweaks. Browse the changelogs matching 7.0.0-alpha.*, 7.0.0-beta.*, and 7.0.0-rc.* for the full list of changes.

See our Migration guide to upgrade from earlier versions of Storybook.

Bug Fixes
  • CLI: Improve incompatible addons logic #​21883

v7.0.1

Compare Source

Bug Fixes
  • CLI: Always send error events if init doesn't succeed #​21879
  • CLI: Warn when community addons are incompatible with Storybook 7 #​21863
  • CLI: Fix migration summary message #​21862
  • CLI: Fix link to new framework API migrations #​21875
Maintenance
  • Angular: Remove deprecated component/propsMeta from story #​21807
  • Remove deprecated flags and properties #​21852
Dependencies

v7.0.0

Compare Source

Storybook 7.0 is here! 🎉

7.0 contains hundreds more fixes, features, and tweaks. Browse the changelogs matching 7.0.0-alpha.*, 7.0.0-beta.*, and 7.0.0-rc.* for the full list of changes.

See our Migration guide to upgrade from earlier versions of Storybook.

Full announcement and proper release to the latest npm tag coming soon. 😘

testing-library/react-testing-library

v14.0.0

Compare Source

Bug Fixes
Features
BREAKING CHANGES

v13.4.0

Compare Source

Features
  • renderHook: allow passing of all render options to renderHook (#​1118) (27a9584)

v13.3.0

Compare Source

Features

v13.2.0

Compare Source

Features

v13.1.1

Compare Source

Bug Fixes

v13.1.0

Compare Source

Features

v13.0.1

Compare Source

Bug Fixes

v13.0.0

Compare Source

Features
BREAKING CHANGES

v12.1.5

Compare Source

Bug Fixes

v12.1.4

Compare Source

Bug Fixes
  • Match runtime type of baseElement in TypeScript types (#​1023) (96ed8da)

v12.1.3

Compare Source

Bug Fixes

v12.1.2

Compare Source

Bug Fixes
  • render: Don't reject wrapper types based on statics (#​973) (7f53b56)

v12.1.1

Compare Source

Bug Fixes

v12.1.0

Compare Source

Features

v12.0.0

Compare Source

Bug Fixes
Features
BREAKING CHANGES
  • Bump @testing-library/dom to 8.0.0. Please check out the @testing-library/dom@8.0.0 release page for a detailed list of breaking changes.
  • node 10 is no longer supported. It reached its end-of-life on 30.04.2021.
facebook/react

v18.2.0

Compare Source

React DOM
React DOM Server
Server Components (Experimental)

v18.1.0

Compare Source

React DOM
React DOM Server
ESLint Plugin: React Hooks
Use Subscription

v18.0.0

Compare Source

Below is a list of all new features, APIs, deprecations, and breaking changes.
Read React 18 release post and React 18 upgrade guide for more information.

New Features
React
  • useId is a new hook for generating unique IDs on both the client and server, while avoiding hydration mismatches. It is primarily useful for component libraries integrating with accessibility APIs that require unique IDs. This solves an issue that already exists in React 17 and below, but it’s even more important in React 18 because of how the new streaming server renderer delivers HTML out-of-order.
  • startTransition and useTransition let you mark some state updates as not urgent. Other state updates are considered urgent by default. React will allow urgent state updates (for example, updating a text input) to interrupt non-urgent state updates (for example, rendering a list of search results).
  • useDeferredValue lets you defer re-rendering a non-urgent part of the tree. It is similar to debouncing, but has a few advantages compared to it. There is no fixed time delay, so React will attempt the deferred render right after the first render is reflected on the screen. The deferred render is interruptible and doesn't block user input.
  • useSyncExternalStore is a new hook that allows external stores to support concurrent reads by forcing updates to the store to be synchronous. It removes the need for useEffect when implementing subscriptions to external data sources, and is recommended for any library that integrates with state external to React.
  • useInsertionEffect is a new hook that allows CSS-in-JS libraries to address performance issues of injecting styles in render. Unless you’ve already built a CSS-in-JS library we don’t expect you to ever use this. This hook will run after the DOM is mutated, but before layout effects read the new layout. This solves an issue that already exists in React 17 and below, but is even more important in React 18 because React yields to the browser during concurrent rendering, giving it a chance to recalculate layout.
React DOM Client

These new APIs are now exported from react-dom/client:

  • createRoot: New method to create a root to render or unmount. Use it instead of ReactDOM.render. New features in React 18 don't work without it.
  • hydrateRoot: New method to hydrate a server rendered application. Use it instead of ReactDOM.hydrate in conjunction with the new React DOM Server APIs. New features in React 18 don't work without it.

Both createRoot and hydrateRoot accept a new option called onRecoverableError in case you want to be notified when React recovers from errors during rendering or hydration for logging. By default, React will use reportError, or console.error in the older browsers.

React DOM Server

These new APIs are now exported from react-dom/server and have full support for streaming Suspense on the server:

  • renderToPipeableStream: for streaming in Node environments.
  • renderToReadableStream: for modern edge runtime environments, such as Deno and Cloudflare workers.

The existing renderToString method keeps working but is discouraged.

remix-run/react-router

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

v6.10.0

Compare Source

Minor Changes

  • Added support for Future Flags in React Router. The first flag being introduced is future.v7_normalizeFormMethod which will normalize the exposed useNavigation()/useFetcher() formMethod fields as uppercase HTTP methods to align with the fetch() behavior. (#​10207)

    • When future.v7_normalizeFormMethod === false (default v6 behavior),
      • useNavigation().formMethod is lowercase
      • useFetcher().formMethod is lowercase
    • When future.v7_normalizeFormMethod === true:
      • useNavigation().formMethod is uppercase
      • useFetcher().formMethod is uppercase
Patch Changes
  • Fix createStaticHandler to also check for ErrorBoundary on routes in addition to errorElement (#​10190)
  • Updated dependencies:
    • @remix-run/router@1.5.0
    • react-router@6.10.0

v6.9.0

Compare Source

Minor Changes

  • React Router now supports an alternative way to define your route element and errorElement fields as React Components instead of React Elements. You can instead pass a React Component to the new Component and ErrorBoundary fields if you choose. There is no functional difference between the two, so use whichever approach you prefer 😀. You shouldn't be defining both, but if you do Component/ErrorBoundary will "win". (#​10045)

    Example JSON Syntax

    // Both of these work the same:
const elementRoutes = [{
  path: '/',
  element: <Home />,
  errorElement: <HomeError />,
}]

const componentRoutes = [{
  path: '/',
  Component: Home,
  ErrorBoundary: HomeError,
}]

function Home() { ... }
function HomeError() { ... }

    Example JSX Syntax

    // Both of these work the same:
const elementRoutes = createRoutesFromElements(
  <Route path='/' element={<Home />} errorElement={<HomeError /> } />
);

const componentRoutes = createRoutesFromElements(
  <Route path='/' Component={Home} ErrorBoundary={HomeError} />
);

function Home() { ... }
function HomeError() { ... }

  • Introducing Lazy Route Modules! (#​10045)

    In order to keep your application bundles small and support code-splitting of your routes, we've introduced a new lazy() route property. This is an async function that resolves the non-route-matching portions of your route definition (loader, action, element/Component, errorElement/ErrorBoundary, shouldRevalidate, handle).

    Lazy routes are resolved on initial load and during the loading or submitting phase of a navigation or fetcher call. You cannot lazily define route-matching properties (path, index, children) since we only execute your lazy route functions after we've matched known routes.

    Your lazy functions will typically return the result of a dynamic import.

    // In this example, we assume most folks land on the homepage so we include that
// in our critical-path bundle, but then we lazily load modules for /a and /b so
// they don't load until the user navigates to those routes
let routes = createRoutesFromElements(
  <Route path="/" element={<Layout />}>
    <Route index element={<Home />} />
    <Route path="a" lazy={() => import("./a")} />
    <Route path="b" lazy={() => import("./b")} />
  </Route>
);

    Then in your lazy route modules, export the properties you want defined for the route:

    export async function loader({ request }) {
  let data = await fetchData(request);
  return json(data);
}

// Export a `Component` directly instead of needing to create a React Element from it
export function Component() {
  let data = useLoaderData();

  return (
    <>
      <h1>You made it!</h1>
      <p>{data}</p>
    </>
  );
}

// Export an `ErrorBoundary` directly instead of needing to create a React Element from it
export function ErrorBoundary() {
  let error = useRouteError();
  return isRouteErrorResponse(error) ? (
    <h1>
      {error.status} {error.statusText}
    </h1>
  ) : (
    <h1>{error.message || error}</h1>
  );
}

    An example of this in action can be found in the examples/lazy-loading-router-provider directory of the repository.

    🙌 Huge thanks to @​rossipedia for the Initial Proposal and POC Implementation.

  • Updated dependencies:

    • react-router@6.9.0
    • @remix-run/router@1.4.0

v6.8.2

Compare Source

Patch Changes
  • Treat same-origin absolute URLs in <Link to> as external if they are outside of the router basename (#​10135)
  • Fix useBlocker to return IDLE_BLOCKER during SSR (#​10046)
  • Fix SSR of absolute <Link to> urls (#​10112)
  • Properly escape HTML characters in StaticRouterProvider serialized hydration data (#​10068)
  • Updated dependencies:
    • @remix-run/router@1.3.3
    • react-router@6.8.2

v6.8.1

Compare Source

Patch Changes
  • Improved absolute url detection in Link component (now also supports mailto: urls) (#​9994)
  • Fix partial object (search or hash only) pathnames losing current path value (#​10029)
  • Updated dependencies:
    • react-router@6.8.1
    • @remix-run/router@1.3.2

v6.8.0

Compare Source

Minor Changes

  • Support absolute URLs in <Link to>. If the URL is for the current origin, it will still do a client-side navigation. If the URL is for a different origin then it will do a fresh document request for the new origin. (#​9900)

    <Link to="https://neworigin.com/some/path">    {/* Document request */}
<Link to="//neworigin.com/some/path">          {/* Document request */}
<Link to="https://www.currentorigin.com/path"> {/* Client-side navigation */}
Patch Changes
  • Fix bug with search params removal via useSearchParams (#​9969)
  • Respect preventScrollReset on <fetcher.Form> (#​9963)
  • Fix navigation for hash routers on manual URL changes (#​9980)
  • Use pagehide instead of beforeunload for <ScrollRestoration>. This has better cross-browser support, specifically on Mobile Safari. (#​9945)
  • Updated dependencies:
    • @remix-run/router@1.3.1
    • react-router@6.8.0

v6.7.0

Compare Source

Minor Changes
  • Add unstable_useBlocker hook for blocking navigations within the app's location origin (#​9709)
  • Add unstable_usePrompt hook for blocking navigations within the app's location origin (#​9932)
  • Add preventScrollReset prop to <Form> (#​9886)
Patch Changes
  • Added pass-through event listener options argument to useBeforeUnload (#​9709)
  • Streamline jsdom bug workaround in tests (#​9824)
  • Updated dependencies:
    • @remix-run/router@1.3.0
    • react-router@6.7.0

v6.6.2

Compare Source

Patch Changes
  • Ensure useId consistency during SSR (#​9805)
  • Updated dependencies:
    • react-router@6.6.2

v6.6.1

Compare Source

Patch Changes
  • Updated dependencies:
    • @remix-run/router@1.2.1
    • react-router@6.6.1

v6.6.0

Compare Source

Minor Changes
  • Add useBeforeUnload() hook (#​9664)
  • Remove unstable_ prefix from createStaticHandler/createStaticRouter/StaticRouterProvider (#​9738)
Patch Changes
  • Proper hydration of Error objects from StaticRouterProvider (#​9664)
  • Support uppercase <Form method> and useSubmit method values (#​9664)
  • Skip initial scroll restoration for SSR apps with hydrationData (#​9664)
  • Fix <button formmethod> form submission overriddes (#​9664)
  • Updated dependencies:
    • @remix-run/router@1.2.0
    • react-router@6.6.0

v6.5.0

Compare Source

Patch Changes
  • Updated dependencies:
    • react-router@6.5.0
    • @remix-run/router@1.1.0

v6.4.5

Compare Source

Patch Changes
  • Updated dependencies:
    • @remix-run/router@1.0.5
    • react-router@6.4.5

v6.4.4

Compare Source

Patch Changes
  • Fix issues with encoded characters in NavLink and descendant <Routes> (#​9589, #​9647)
  • Properly serialize/deserialize ErrorResponse instances when using built-in hydration (#​9593)
  • Support basename in static data routers (#​9591)
  • Updated dependencies:
    • @remix-run/router@1.0.4
    • react-router@6.4.4

v6.4.3

Compare Source

Patch Changes
  • Fix hrefs generated for createHashRouter (#​9409)
  • fix encoding/matching issues with special chars (#​9477, #​9496)
  • Properly support index routes with a path in useResolvedPath (#​9486)
  • Respect relative=path prop on NavLink (#​9453)
  • Fix NavLink behavior for root urls (#​9497)
  • Updated dependencies:
    • @remix-run/router@1.0.3
    • react-router@6.4.3

v6.4.2

Compare Source

Patch Changes
  • Respect basename in useFormAction (#​9352)
  • Enhance console error messages for invalid usage of data router hooks (#​9311)
  • If an index route has children, it will result in a runtime error. We have strengthened our RouteObject/RouteProps types to surface the error in TypeScript. (#​9366)
  • Updated dependencies:
    • react-router@6.4.2
    • @remix-run/router@1.0.2

v6.4.1

Compare Source

Patch Changes
  • Updated dependencies:
    • react-router@6.4.1
    • @remix-run/router@1.0.1

v6.4.0

Compare Source

Whoa this is a big one! 6.4.0 brings all the data loading and mutation APIs over from Remix. Here's a quick high level overview, but it's recommended you go check out the docs, especially the feature overview and the tutorial.

New APIs

  • Create your router with createMemoryRouter/createBrowserRouter/createHashRouter
  • Render your router with <RouterProvider>
  • Load data with a Route loader and mutate with a Route action
  • Handle errors with Route errorElement
  • Submit data with the new <Form> component
  • Perform in-page data loads and mutations with useFetcher()
  • Defer non-critical data with defer and Await
  • Manage scroll position with <ScrollRestoration>

New Features

  • Perform path-relative navigations with <Link relative="path"> (#​9160)

Bug Fixes

  • Path resolution is now trailing slash agnostic (#​8861)
  • useLocation returns the scoped location inside a <Routes location> component (#​9094)
  • respect the <Link replace> prop if it is defined (#​8779)

Updated Dependencies

  • react-router@6.4.0

v6.3.0: react-router@v6.3.0

Compare Source

What's Changed

New Contributors

Full Changelog: remix-run/react-router@v6.2.2...v6.3.0

v6.2.2

Compare Source

What's Changed

🐛 Bug Fixes
  • Fixed nested splat routes that begin with special URL-safe characters (#​8563)
  • Fixed a bug where index routes were missing route context in some cases (#​8497)

New Contributors

Configuration

📅 Schedule: Branch creation - "before 8am on the first day of the month" in timezone Australia/Melbourne, 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.

@renovate renovate bot requested a review from a team as a code owner October 31, 2022 18:23
@changeset-bot
Copy link

changeset-bot bot commented Oct 31, 2022 •
edited

⚠️ No Changeset found

Latest commit: ae9a2b7

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

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@renovate renovate bot force-pushed the renovate-major-react-packages branch 3 times, most recently from f2ad416 to c34388d Compare November 3, 2022 22:20
@renovate renovate bot force-pushed the renovate-major-react-packages branch from c34388d to 890700a Compare December 13, 2022 00:02
@renovate renovate bot force-pushed the renovate-major-react-packages branch 2 times, most recently from 011c8de to d774dbe Compare January 24, 2023 03:14
@renovate renovate bot force-pushed the renovate-major-react-packages branch from d774dbe to ff4d889 Compare January 31, 2023 04:20
@renovate renovate bot force-pushed the renovate-major-react-packages branch 7 times, most recently from 7e051cd to 42ad79f Compare February 16, 2023 03:42
@renovate renovate bot force-pushed the renovate-major-react-packages branch from 42ad79f to 4726900 Compare February 16, 2023 23:40
@renovate renovate bot force-pushed the renovate-major-react-packages branch from 4726900 to 7182d5b Compare February 27, 2023 04:39
@renovate renovate bot force-pushed the renovate-major-react-packages branch 5 times, most recently from feef507 to 76fa6e8 Compare March 15, 2023 00:59
@renovate renovate bot force-pushed the renovate-major-react-packages branch 4 times, most recently from 11a13e9 to fb8c5ae Compare March 22, 2023 03:42
@renovate renovate bot changed the title chore(deps): Update react packages (major) fix(deps): Update react packages (major) Mar 22, 2023
@renovate renovate bot force-pushed the renovate-major-react-packages branch 2 times, most recently from 90521a7 to 335fa19 Compare March 30, 2023 22:05
@renovate renovate bot force-pushed the renovate-major-react-packages branch 13 times, most recently from 13601a1 to fb5d775 Compare April 19, 2023 01:49
@renovate renovate bot force-pushed the renovate-major-react-packages branch 2 times, most recently from 3436a1d to 1610f64 Compare April 21, 2023 04:11
@renovate renovate bot force-pushed the renovate-major-react-packages branch 6 times, most recently from 0cc396b to 70eb351 Compare May 2, 2023 05:45
@renovate
Copy link
Contributor Author

renovate bot commented May 3, 2023 •
edited

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml
installing v2 tool node v14.17.4
updating node-gyp
+ node-gyp@9.3.1
added 74 packages from 44 contributors and updated 2 packages in 5.278s
linking tool node v14.17.4
node: v14.17.4 /usr/local/bin/node
npm: 6.14.14  /usr/local/bin/npm
Installed v2 /usr/local/buildpack/tools/v2/node.sh in 8 seconds
installing v2 tool pnpm v8.4.0
+ pnpm@8.4.0
added 1 package in 0.845s
linking tool pnpm v8.4.0
ERROR: This version of pnpm requires at least Node.js v16.14
The current version of Node.js is v14.17.4
Visit https://r.pnpm.io/comp to see the list of past pnpm versions with respective Node.js version support.

@renovate renovate bot force-pushed the renovate-major-react-packages branch 3 times, most recently from 58f6ede to 0e3a203 Compare May 4, 2023 05:21
@renovate renovate bot force-pushed the renovate-major-react-packages branch from 0e3a203 to ae9a2b7 Compare May 4, 2023 22:54
@askoufis
Copy link
Contributor

askoufis commented May 5, 2023 •
edited

Superseded by #790, though it doesn't touch react router or storybook.

@askoufis askoufis closed this May 5, 2023
@askoufis askoufis deleted the renovate-major-react-packages branch May 5, 2023 00:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
1 participant
@askoufis