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 remix monorepo to v2.16.2 #9

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 16, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@remix-run/css-bundle (source) 2.7.2 -> 2.16.2 age adoption passing confidence
@remix-run/dev (source) 2.7.2 -> 2.16.2 age adoption passing confidence
@remix-run/eslint-config (source) 2.7.2 -> 2.16.2 age adoption passing confidence
@remix-run/node (source) 2.7.2 -> 2.16.2 age adoption passing confidence
@remix-run/react (source) 2.7.2 -> 2.16.2 age adoption passing confidence
@remix-run/serve (source) 2.7.2 -> 2.16.2 age adoption passing confidence

Release Notes

remix-run/remix (@​remix-run/css-bundle)

v2.16.2

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.16.2.

v2.16.1

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.16.1.

v2.16.0

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.16.0.

v2.15.3

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.15.3.

v2.15.2

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.15.2.

v2.15.1

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.15.1.

v2.15.0

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.15.0.

v2.14.0

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.14.0.

v2.13.1

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.13.1.

v2.13.0

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.13.0.

v2.12.1

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.12.1.

v2.12.0

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.12.0.

v2.11.2

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.11.2.

v2.11.1

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.11.1.

v2.11.0

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.11.0.

v2.10.3

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.10.3.

v2.10.2

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.10.2.

v2.10.1

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.10.1.

v2.10.0

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.10.0.

v2.9.2

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.9.2.

v2.9.1

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.9.1.

v2.9.0

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.9.0.

v2.8.1

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.8.1.

v2.8.0

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.8.0.

remix-run/remix (@​remix-run/dev)

v2.16.2

Compare Source

Patch Changes

v2.16.1

Compare Source

Patch Changes
  • When future.v3_routeConfig is enabled, fix errors evaluating routes.ts when multiple copies of @remix-run/dev are present (#​10524)
  • Remove unused Vite file system watcher (#​10510)
  • Fix Vite import analysis of @remix-run/react failing when the package is not marked as external (#​10528)
  • Updated dependencies:

v2.16.0

Compare Source

Minor Changes
Patch Changes

v2.15.3

Compare Source

Patch Changes

v2.15.2

Compare Source

Patch Changes

v2.15.1

Compare Source

Patch Changes

v2.15.0

Compare Source

Patch Changes
  • Stabilize the future.v3_routeConfig future flag, replacing future.unstable_routeConfig. This enables support for routes.ts to assist with the migration to React Router v7. (#​10236)

    Note that if you had already enabled the future.unstable_routeConfig flag, your route config in app/routes.ts is no longer defined via the routes export and must now be defined via the default export.

    import { type RouteConfig } from "@​remix-run/route-config";
    
    -export const routes: RouteConfig = [];
    +export default [] satisfies RouteConfig;
  • Updated dependencies:

v2.14.0

Compare Source

Minor Changes
  • Add support for routes.ts behind future.unstable_routeConfig flag to assist with the migration to React Router v7. (#​10107)

    Config-based routing is the new default in React Router v7, configured via the routes.ts file in the app directory. Support for routes.ts and its related APIs in Remix are designed as a migration path to help minimize the number of changes required when moving your Remix project over to React Router v7. While some new packages have been introduced within the @remix-run scope, these new packages only exist to keep the code in routes.ts as similar as possible to the equivalent code for React Router v7.

    When the unstable_routeConfig future flag is enabled, Remix's built-in file system routing will be disabled and your project will opted into React Router v7's config-based routing.

    To enable the flag, in your vite.config.ts file:

    remix({
      future: {
        unstable_routeConfig: true,
      },
    });

    A minimal routes.ts file to support Remix's built-in file system routing looks like this:

    // app/routes.ts
    import { flatRoutes } from "@​remix-run/fs-routes";
    import type { RouteConfig } from "@​remix-run/route-config";
    
    export const routes: RouteConfig = flatRoutes();
  • Log deprecation warnings for v3 future flags (#​10126)

    • Add @deprecated annotations to json/defer utilities
Patch Changes

v2.13.1

Compare Source

Patch Changes

v2.13.0

Compare Source

Minor Changes
  • Stabilize the future.unstable_optimizeDeps flag into future.v3_optimizeDeps (#​10092)
  • Stabilize React Router APIs in Remix (#​9980)
    • Adopt stabilized React Router APIs internally
      • Single Fetch: unstable_dataStrategy -> dataStrategy
      • Lazy Route Discovery: unstable_patchRoutesOnNavigation -> patchRoutesOnNavigation
    • Stabilize public-facing APIs
      • Single Fetch: unstable_data() -> data()
      • unstable_viewTransition -> viewTransition (Link, Form, navigate, submit)
      • unstable_flushSync> -> <Link viewTransition> (Link, Form, navigate, submit, useFetcher)
  • Stabilize future flags (#​10072)
    • future.unstable_singleFetch -> future.v3_singleFetch
    • future.unstable_lazyRouteDiscovery -> future.v3_lazyRouteDiscovery
Patch Changes
  • Stop passing request.signal as the renderToReadableStream signal to abort server rendering for cloudflare/deno runtimes because by the time that request is aborted, aborting the rendering is useless because there's no way for React to flush down the unresolved boundaries (#​10047)

    • This has been incorrect for some time, but only recently exposed due to a bug in how we were aborting requests when running via remix vite:dev because we were incorrectly aborting requests after successful renders - which was causing us to abort a completed React render, and try to close an already closed ReadableStream.
    • This has likely not shown up in any production scenarios because cloudflare/deno production runtimes are (correctly) not aborting the request.signal on successful renders
    • The built-in entry.server files no longer pass a signal to renderToReadableStream because adding a timeout-based abort signal to the default behavior would constitute a breaking change
    • Users can configure this abort behavior via their own entry.server via remix reveal entry.server, and the template entry.server files have been updated with an example approach for newly created Remix apps
  • Fix adapter logic for aborting request.signal so we don't incorrectly abort on the close event for successful requests (#​10046)

  • Updated dependencies:

v2.12.1

Compare Source

Patch Changes
  • Properly abort request.signal during vite dev when the node response is closed (#​9976)
  • CSS imports with ?inline, ?inline-css and ?raw are no longer incorrectly injected during SSR in development (#​9910)
  • Updated dependencies:

v2.12.0

Compare Source

Minor Changes
  • New future.unstable_optimizeDeps flag for automatic dependency optimization (#​9921)
    • You can now opt-in to automatic dependency optimization during development by using the future.unstable_optimizeDeps future flag
    • For details, check out the docs at Guides > Dependency optimization
    • For users who were previously working around this limitation, you no longer need to explicitly add routes to Vite's optimizeDeps.entries nor do you need to disable the remix-dot-server plugin
Patch Changes
  • Handle circular dependencies in modulepreload manifest generation (#​9917)
  • Fix dest already exists build errors by only moving SSR assets to the client build directory when they're not already present on disk (#​9901)
  • Updated dependencies:

v2.11.2

Compare Source

Patch Changes

v2.11.1

Compare Source

Patch Changes

v2.11.0

Compare Source

Minor Changes
  • Rename future.unstable_fogOfWar to future.unstable_lazyRouteDiscovery for clarity (#​9763)
Patch Changes

v2.10.3

Compare Source

Patch Changes

v2.10.2

Compare Source

Patch Changes

v2.10.1

Compare Source

Patch Changes

v2.10.0

Compare Source

Patch Changes

v2.9.2

Compare Source

Patch Changes
  • Fix dest already exists error when running remix vite:build (#​9305)
  • Vite: Fix issue resolving critical CSS during development when route files are located outside of the app directory. (#​9194)
  • Remove @remix-run/node from Vite plugin's optimizeDeps.include list since it was unnecessary and resulted in Vite warnings when not depending on this package. (#​9287)
  • Clean up redundant ?client-route=1 imports in development (#​9395)
  • Ensure Babel config files are not referenced when applying the react-refresh Babel transform within the Remix Vite plugin (#​9241)
  • Updated dependencies:

v2.9.1

Compare Source

Patch Changes
  • Fix issue where consumers who had added Remix packages to Vite's ssr.noExternal option were being overridden by the Remix Vite plugin adding Remix packages to Vite's ssr.external option (#​9301)
  • Updated dependencies:

v2.9.0

Compare Source

Minor Changes
  • New future.unstable_singleFetch flag (#​8773)

    • Naked objects returned from loaders/actions are no longer automatically converted to JSON responses. They'll be streamed as-is via turbo-stream so Date's will become Date through useLoaderData()
    • You can return naked objects with Promise's without needing to use defer() - including nested Promise's
      • If you need to return a custom status code or custom response headers, you can still use the defer utility
    • <RemixServer abortDelay> is no longer used. Instead, you should export const streamTimeout from entry.server.tsx and the remix server runtime will use that as the delay to abort the streamed response
      • If you export your own streamTimeout, you should decouple that from aborting the react renderToPipeableStream. You should always ensure that react is aborted afer the stream is aborted so that abort rejections can be flushed down
    • Actions no longer automatically revalidate on 4xx/5xx responses (via RR future.unstable_skipActionErrorRevalidation flag) - you can return a 2xx to opt-into revalidation or use shouldRevalidate
Patch Changes
  • Improve getDependenciesToBundle resolution in monorepos (#​8848)
  • Fix SPA mode when single fetch is enabled by using streaming entry.server (#​9063)
  • Vite: added sourcemap support for transformed routes (#​8970)
  • Update links printed to the console by the Remix CLI/Dev Server to point to updated docs locations (#​9176)
  • Updated dependencies:

v2.8.1

Compare Source

Patch Changes
  • Support reading from Vite config when running remix reveal and remix routes CLI commands (#​8916)
  • Add Vite commands to Remix CLI --help output (#​8939)
  • Vite: Fix support for build.sourcemap option in Vite config (#​8965)
  • Clean up redundant client route query strings on route JavaScript files in production builds (#​8969)
  • Vite: Fix error when using Vite's server.fs.allow option without a client entry file (#​8966)
  • Updated dependencies:

v2.8.0

Compare Source

Minor Changes
  • Pass resolved viteConfig to Remix Vite plugin's buildEnd hook (#​8885)
Patch Changes
  • Mark Layout as browser safe route export in esbuild compiler (#​8842)
  • Vite: Silence build warnings when dependencies include "use client" directives (#​8897)
  • Vite: Fix serverBundles issue where multiple browser manifests are generated (#​8864)
  • Support custom Vite build.assetsDir option (#​8843)
  • Updated dependencies:
remix-run/remix (@​remix-run/eslint-config)

v2.16.2

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.16.2.

v2.16.1

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.16.1.

v2.16.0

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.16.0.

v2.15.3

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.15.3.

v2.15.2

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.15.2.

v2.15.1

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.15.1.

v2.15.0

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.15.0.

v2.14.0

Compare Source

Minor Changes
  • Add deprecation warning to @remix-run/eslint-config (#​10174)

v2.13.1

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.13.1.

v2.13.0

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.13.0.

v2.12.1

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.12.1.

v2.12.0

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.12.0.

v2.11.2

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.11.2.

v2.11.1

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.11.1.

v2.11.0

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.11.0.

v2.10.3

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.10.3.

v2.10.2

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.10.2.

v2.10.1

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.10.1.

v2.10.0

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.10.0.

v2.9.2

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.9.2.

v2.9.1

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.9.1.

v2.9.0

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.9.0.

v2.8.1

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.8.1.

v2.8.0

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.8.0.

remix-run/remix (@​remix-run/node)

v2.16.2

Compare Source

Patch Changes

v2.16.1

Compare Source

Patch Changes

v2.16.0

Compare Source

Patch Changes

v2.15.3

Compare Source

Patch Changes

v2.15.2

Compare Source

Patch Changes

v2.15.1

Compare Source

Patch Changes

v2.15.0

Compare Source

Patch Changes

v2.14.0

Compare Source

Patch Changes

v2.13.1

Compare Source

Patch Changes

v2.13.0

Compare Source

Patch Changes

v2.12.1

Compare Source

Patch Changes
  • Single Fetch: Re-export interface Future through @remix-run/node/@remix-run/cloudflare/@remix-run/deno packages so that pnpm doesn't complain about @remix-run/server-runtime not being a dependency (#​9982)
  • Updated dependencies:

v2.12.0

Compare Source

Patch Changes
  • Single Fetch: Improved typesafety (#​9893)

    If you were already using previously released unstable single-fetch types:

    • Remove "@&#8203;remix-run/react/future/single-fetch.d.ts" override from tsconfig.json > compilerOptions > types
    • Remove defineLoader, defineAction, defineClientLoader, defineClientAction helpers from your route modules
    • Replace UIMatch_SingleFetch type helper with UIMatch
    • Replace MetaArgs_SingleFetch type helper with MetaArgs

    Then you are ready for the new typesafety setup:

    // vite.config.ts
    
    declare module "@&#8203;remix-run/server-runtime" {
      interface Future {
        unstable_singleFetch: true; // 👈 enable _types_ for single-fetch
      }
    }
    
    export default defineConfig({
      plugins: [
        remix({
          future: {
            unstable_singleFetch: true, // 👈 enable single-fetch
          },
        }),
      ],
    });

    For more information, see Guides > Single Fetch in our docs.

  • Updated dependencies:

v2.11.2

Compare Source

Patch Changes

v2.11.1

Compare Source

Patch Changes

v2.11.0

Compare Source

Minor Changes
  • Single Fetch: Add a new unstable_data() API as a replacement for json/defer when custom status/headers are needed (#​9769)
  • Add a new replace(url, init?) alternative to redirect(url, init?) that performs a history.replaceState instead of a history.pushState on client-side navigation redirects (#​9764)
Patch Changes

v2.10.3

Compare Source

Patch Changes

v2.10.2

Compare Source

Patch Changes

v2.10.1

Compare Source

Patch Changes

v2.10.0

Compare Source

Patch Changes

v2.9.2

Compare Source

Patch Changes
  • Typesafety for single-fetch: defineLoader, defineClientLoader, defineAction, defineClientAction (#​9372, #​9404)
  • Updated dependencies:

v2.9.1

Compare Source

Patch Changes

v2.9.0

Compare Source

Minor Changes
  • Use undici as our fetch polyfill going forward (#​9106, #​9111)
  • Put undici fetch polyfill behind a new installGlobals({ nativeFetch: true }) parameter (#​9198)
    • remix-serve will default to using undici for the fetch polyfill if future._unstable_singleFetch is enabled because the single fetch implementation relies on the undici polyfill
      • Any users opting into Single Fetch and managing their own polfill will need to pass the flag to installGlobals on their own to avoid runtime errors with Single Fetch
Patch Changes

v2.8.1

Compare Source

Patch Changes

v2.8.0

Compare Source

Patch Changes
remix-run/remix (@​remix-run/react)

v2.16.2

Compare Source

Patch Changes
  • Fix shouldRevalidate behavior for `clientLo

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 is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


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

This PR was generated by Mend Renovate. View the repository job log.

Sorry, something went wrong.

@renovate renovate bot force-pushed the renovate/remix-monorepo branch 5 times, most recently from 3622abb to c67239a Compare February 16, 2024 13:44
@renovate renovate bot force-pushed the renovate/remix-monorepo branch 2 times, most recently from d305697 to 20fc06e Compare February 23, 2024 03:19
@renovate renovate bot changed the title fix(deps): update remix monorepo to v1.19.3 fix(deps): update remix monorepo to v1.19.3 - autoclosed Feb 23, 2024
@renovate renovate bot closed this Feb 23, 2024
@renovate renovate bot deleted the renovate/remix-monorepo branch February 23, 2024 03:21
@renovate renovate bot changed the title fix(deps): update remix monorepo to v1.19.3 - autoclosed fix(deps): update remix monorepo to v1.19.3 Feb 29, 2024
@renovate renovate bot reopened this Feb 29, 2024
@renovate renovate bot restored the renovate/remix-monorepo branch February 29, 2024 01:30
@renovate renovate bot force-pushed the renovate/remix-monorepo branch from 20fc06e to cd2888a Compare February 29, 2024 01:31
@renovate renovate bot changed the title fix(deps): update remix monorepo to v1.19.3 fix(deps): update remix monorepo to v2.8.0 Feb 29, 2024
@renovate renovate bot changed the title fix(deps): update remix monorepo to v2.8.0 fix(deps): update remix monorepo to v2.8.1 Mar 7, 2024
@renovate renovate bot force-pushed the renovate/remix-monorepo branch from cd2888a to da139bc Compare March 7, 2024 18:50
@renovate renovate bot force-pushed the renovate/remix-monorepo branch from da139bc to 36879b1 Compare April 23, 2024 17:24
@renovate renovate bot changed the title fix(deps): update remix monorepo to v2.8.1 fix(deps): update remix monorepo to v2.9.0 Apr 23, 2024
@renovate renovate bot force-pushed the renovate/remix-monorepo branch from 36879b1 to e8ffdcc Compare April 24, 2024 16:32
@renovate renovate bot changed the title fix(deps): update remix monorepo to v2.9.0 fix(deps): update remix monorepo to v2.9.1 Apr 24, 2024
@renovate renovate bot force-pushed the renovate/remix-monorepo branch from e8ffdcc to 244a850 Compare May 10, 2024 19:11
@renovate renovate bot changed the title fix(deps): update remix monorepo to v2.9.1 fix(deps): update remix monorepo to v2.9.2 May 10, 2024
@renovate renovate bot force-pushed the renovate/remix-monorepo branch from 244a850 to a936a82 Compare June 25, 2024 16:26
@renovate renovate bot changed the title fix(deps): update remix monorepo to v2.9.2 fix(deps): update remix monorepo to v2.10.0 Jun 25, 2024
@renovate renovate bot force-pushed the renovate/remix-monorepo branch from a936a82 to 82a8937 Compare July 3, 2024 16:31
@renovate renovate bot changed the title fix(deps): update remix monorepo to v2.10.0 fix(deps): update remix monorepo to v2.10.1 Jul 3, 2024
@renovate renovate bot force-pushed the renovate/remix-monorepo branch from 82a8937 to f478519 Compare July 4, 2024 15:10
@renovate renovate bot changed the title fix(deps): update remix monorepo to v2.10.1 fix(deps): update remix monorepo to v2.10.2 Jul 4, 2024
@renovate renovate bot force-pushed the renovate/remix-monorepo branch from f478519 to cb5a387 Compare July 16, 2024 16:38
@renovate renovate bot force-pushed the renovate/remix-monorepo branch from 44952f3 to 0461173 Compare September 19, 2024 18:22
@renovate renovate bot changed the title fix(deps): update remix monorepo to v2.12.0 fix(deps): update remix monorepo to v2.12.1 Sep 19, 2024
@renovate renovate bot force-pushed the renovate/remix-monorepo branch from 0461173 to 4bd3d19 Compare October 11, 2024 20:11
@renovate renovate bot changed the title fix(deps): update remix monorepo to v2.12.1 fix(deps): update remix monorepo to v2.13.0 Oct 11, 2024
@renovate renovate bot force-pushed the renovate/remix-monorepo branch from 4bd3d19 to 41e45c9 Compare October 12, 2024 02:17
@renovate renovate bot changed the title fix(deps): update remix monorepo to v2.13.0 fix(deps): update remix monorepo to v2.13.1 Oct 12, 2024
@renovate renovate bot force-pushed the renovate/remix-monorepo branch from 41e45c9 to 7bb1716 Compare November 9, 2024 00:26
@renovate renovate bot changed the title fix(deps): update remix monorepo to v2.13.1 fix(deps): update remix monorepo to v2.14.0 Nov 9, 2024
@renovate renovate bot force-pushed the renovate/remix-monorepo branch from 7bb1716 to 1cdde1d Compare November 22, 2024 11:38
@renovate renovate bot changed the title fix(deps): update remix monorepo to v2.14.0 fix(deps): update remix monorepo to v2.15.0 Nov 22, 2024
@renovate renovate bot force-pushed the renovate/remix-monorepo branch from 1cdde1d to 0f41033 Compare December 9, 2024 20:36
@renovate renovate bot changed the title fix(deps): update remix monorepo to v2.15.0 fix(deps): update remix monorepo to v2.15.1 Dec 9, 2024
@renovate renovate bot force-pushed the renovate/remix-monorepo branch from 0f41033 to 1da19c6 Compare December 21, 2024 00:38
@renovate renovate bot changed the title fix(deps): update remix monorepo to v2.15.1 fix(deps): update remix monorepo to v2.15.2 Dec 21, 2024
@renovate renovate bot force-pushed the renovate/remix-monorepo branch 2 times, most recently from d5cbceb to f2b92a4 Compare January 30, 2025 15:53
@renovate renovate bot force-pushed the renovate/remix-monorepo branch from f2b92a4 to 0bbd7b4 Compare January 30, 2025 20:18
@renovate renovate bot changed the title fix(deps): update remix monorepo to v2.15.2 fix(deps): update remix monorepo to v2.15.3 Jan 30, 2025
@renovate renovate bot force-pushed the renovate/remix-monorepo branch from 0bbd7b4 to 87e0ec6 Compare February 9, 2025 16:03
@renovate renovate bot force-pushed the renovate/remix-monorepo branch from 87e0ec6 to 2a0d14d Compare February 27, 2025 20:36
@renovate renovate bot changed the title fix(deps): update remix monorepo to v2.15.3 fix(deps): update remix monorepo to v2.16.0 Feb 27, 2025
@renovate renovate bot force-pushed the renovate/remix-monorepo branch from 2a0d14d to 7f561f2 Compare March 3, 2025 13:10
@renovate renovate bot force-pushed the renovate/remix-monorepo branch 4 times, most recently from e067a86 to 527a559 Compare March 17, 2025 19:25
@renovate renovate bot changed the title fix(deps): update remix monorepo to v2.16.0 fix(deps): update remix monorepo to v2.16.1 Mar 17, 2025

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
@renovate renovate bot force-pushed the renovate/remix-monorepo branch from 527a559 to 0eb70e1 Compare March 19, 2025 14:42
@renovate renovate bot changed the title fix(deps): update remix monorepo to v2.16.1 fix(deps): update remix monorepo to v2.16.2 Mar 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants