React-GIS Dependency Updates & Dashboard

by Admin 41 views
React-GIS Dependency Dashboard

Hey guys! This is your go-to spot for keeping tabs on all the dependency updates and general dependency health of the React-GIS project. Think of this as your one-stop dashboard for all things dependency-related. Let's dive in!

View this repository on the Mend.io Web Portal.

Config Migration Needed

Before we get started, there's a little housekeeping. We need to migrate the config.

  • [ ] Select this checkbox to let Renovate create an automated Config Migration PR.

Pending Approval

Alright, buckle up! We've got a few branches waiting for your golden touch of approval. These are like little presents, just waiting to be unwrapped (aka, merged!).

  • [ ] chore(deps): update actions/setup-node action to v6
  • [ ] chore(deps): update dependency @types/node to v24
  • [ ] chore(deps): update nextjs-fumadocs (major) (@next/eslint-plugin-next, fumadocs-core, fumadocs-mdx, fumadocs-ui, next)
  • [ ] 🔐 Create all pending approval PRs at once 🔐

Deep Dive into Pending Approvals

actions/setup-node action to v6: This update ensures we're running the latest and greatest version of the actions/setup-node action, which is crucial for setting up our Node.js environment in GitHub Actions workflows. By upgrading, we benefit from the latest features, bug fixes, and security patches. It's like giving our CI/CD pipeline a fresh coat of paint and a tune-up, ensuring everything runs smoothly and efficiently. Keeping this action up-to-date minimizes potential compatibility issues and maximizes performance during builds and tests.

dependency @types/node to v24: Updating the @types/node dependency to version 24 brings us the latest TypeScript definitions for Node.js APIs. This is super important because it allows our codebase to stay aligned with the newest Node.js features and ensures that our TypeScript compiler can accurately type-check our code. By having precise type definitions, we can catch errors early, improve code maintainability, and enhance the overall development experience. Think of it as giving our code a detailed map, so it knows exactly where to go and what to expect.

nextjs-fumadocs (major): This is a big one! Updating nextjs-fumadocs involves several key packages (@next/eslint-plugin-next, fumadocs-core, fumadocs-mdx, fumadocs-ui, next). A major update means there might be breaking changes, but it also brings significant improvements, new features, and optimizations. It's like renovating our entire documentation system, making it more robust, user-friendly, and feature-rich. However, be sure to review the changes carefully to ensure compatibility with our existing setup.

Awaiting Schedule

These updates are patiently waiting for their scheduled time to shine. But if you're feeling impatient (we've all been there!), you can manually trigger them.

  • [ ] chore(deps): update all non-major dependencies (@eslint/js, @next/eslint-plugin-next, @storybook/addon-a11y, @storybook/addon-docs, @storybook/addon-vitest, @storybook/react-vite, @types/node, @vitest/browser-playwright, @vitest/coverage-v8, @vitest/spy, @vitest/ui, eslint, eslint-plugin-storybook, eslint-plugin-turbo, globals, lucide-react, next, node, storybook, storybook-addon-deep-controls, turbo, typescript-eslint, vitest, wrangler)
  • [ ] chore(deps): lock file maintenance

Diving Deeper into Scheduled Updates

Update all non-major dependencies: This update sweeps through a multitude of packages, ensuring we're running the latest minor and patch versions. These updates typically include bug fixes, performance improvements, and small feature enhancements without introducing breaking changes. By keeping these dependencies up-to-date, we maintain a stable and efficient development environment. It’s like regularly servicing our car to ensure it runs smoothly and reliably.

Lock file maintenance: Maintaining the lock file (package-lock.json or pnpm-lock.yaml) is crucial for ensuring consistent and reproducible builds. This update ensures that our lock file accurately reflects the versions of our dependencies, preventing unexpected issues caused by version mismatches. Think of it as creating a detailed blueprint of our project's dependencies, so everyone builds from the same foundation.

Detected Dependencies

Here's a breakdown of all the dependencies Renovate has detected. This is like a peek under the hood to see what makes React-GIS tick.

GitHub Actions

These are the actions that power our CI/CD pipelines. Let's keep them in tip-top shape!

  • actions/checkout v5.0.0
  • pnpm/action-setup v4.2.0
  • actions/setup-node v5.0.0
  • actions/cache v4.3.0
  • changesets/action v1.5.3

npm

Our trusty Node Package Manager dependencies. These are the building blocks of our application.

  • @opennextjs/cloudflare 1.11.0

  • @radix-ui/react-collapsible 1.1.12

  • @radix-ui/react-navigation-menu 1.2.14

  • @radix-ui/react-popover 1.1.15

  • @radix-ui/react-presence 1.1.5

  • @radix-ui/react-scroll-area 1.2.10

  • class-variance-authority 0.7.1

  • fumadocs-core 15.8.5

  • fumadocs-mdx 12.0.3

  • fumadocs-ui 15.8.5

  • lucide-react 0.548.0

  • next 15.5.5

  • next-themes 0.4.6

  • react 19.2.0

  • react-dom 19.2.0

  • tailwind-merge 3.3.1

  • @tailwindcss/postcss 4.1.16

  • @types/mdx 2.0.13

  • @types/node 22.18.10

  • @types/react 19.2.2

  • @types/react-dom 19.2.2

  • postcss 8.5.6

  • tailwindcss 4.1.16

  • typescript 5.9.3

  • wrangler 4.45.2

  • ol 10.6.1

  • react 19.2.0

  • react-dom 19.2.0

  • @storybook/addon-a11y 10.0.1

  • @storybook/addon-docs 10.0.1

  • @storybook/addon-vitest 10.0.1

  • @storybook/react-vite 10.0.1

  • @types/react 19.2.2

  • @types/react-dom 19.2.2

  • @vitejs/plugin-react 5.1.0

  • @vitest/browser-playwright 4.0.5

  • @vitest/coverage-v8 4.0.5

  • @vitest/spy 4.0.5

  • playwright 1.56.1

  • storybook 10.0.1

  • storybook-addon-deep-controls 0.9.5

  • typescript 5.9.3

  • vite 7.1.12

  • vite-tsconfig-paths 5.1.4

  • vitest 4.0.5

  • @changesets/cli 2.29.7

  • @tanstack/config 0.22.0

  • @types/node 22.18.10

  • @vitest/ui 4.0.5

  • eslint 9.38.0

  • prettier 3.6.2

  • publint 0.3.15

  • turbo 2.5.8

  • typedoc 0.28.14

  • typedoc-plugin-frontmatter 1.3.0

  • typedoc-plugin-markdown 4.9.0

  • typescript 5.9.3

  • vitest 4.0.5

  • node >=22

  • pnpm 10.20.0

  • @types/react 19.2.2

  • @types/react-dom 19.2.2

  • @vitejs/plugin-react 5.1.0

  • typescript 5.9.3

  • vite 7.1.12

  • @eslint/compat 1.4.1

  • @eslint/js 9.38.0

  • @next/eslint-plugin-next 15.5.5

  • eslint 9.38.0

  • eslint-config-prettier 10.1.8

  • eslint-plugin-react 7.37.5

  • eslint-plugin-react-hooks 7.0.1

  • eslint-plugin-react-refresh 0.4.24

  • eslint-plugin-storybook 10.0.1

  • eslint-plugin-turbo 2.5.8

  • globals 16.4.0

  • prettier 3.6.2

  • typescript 5.9.3

  • typescript-eslint 8.46.2

  • @ianvs/prettier-plugin-sort-imports 4.7.0

  • prettier 3.6.2

  • prettier-plugin-tailwindcss 0.7.1

  • typescript 5.9.3

  • @total-typescript/ts-reset 0.6.1

nvm

Node Version Manager keeps our Node.js version consistent across environments.

  • node 24.8.0
  • [ ] Check this box to trigger a request for Renovate to run again on this repository