Update all outdated dependencies to latest#98
Merged
Conversation
Bump every outdated gem and npm package to its newest version, including the major-version upgrades, and apply the required migrations. Gems: - inertia_rails 3.10 -> 3.21 (Inertia.js v3) - clerk-sdk-ruby 4.2 -> 5.1, jwt 2 -> 3 - sentry-ruby/-rails 5.26 -> 6.6 - puma 6 -> 8, solid_cable 3 -> 4, kamal 2.7 -> 2.11, propshaft 1.2 -> 1.3 - plus all remaining minor/patch bumps (bootsnap, faraday, rspec, etc.) npm: - @inertiajs/react 2 -> 3 (Inertia.js v3 client) - vite 7 -> 8, @vitejs/plugin-react 4 -> 6, typescript 5 -> 6 - lucide-react <1 -> 1.17, globals 16 -> 17, prettier-plugin-tailwindcss 0.6 -> 0.8, @sentry/react 10.55 -> 10.56 Inertia.js v3 migration: - Enable the v3-required server settings (script element for the initial page, data-inertia head attribute, always include the errors hash). - Rename the managed <title> attribute from `inertia` to `data-inertia`. TypeScript 6: drop the now-deprecated `baseUrl` compiler option; `paths` resolve relative to each tsconfig, so the `@/*` alias is unchanged. eslint is intentionally held at 9.x: its latest 10 release has no compatible eslint-plugin-react / eslint-plugin-import release yet. Verified: tsc, eslint, prettier, vitest, client + SSR Vite builds, npm audit (0 high), rubocop, brakeman, and the full RSpec suite (63 examples, 0 failures) all pass. https://claude.ai/code/session_01D4qYdK1vwbg19M2TB2D386
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Brings every outdated gem and npm package up to its newest version, including the major-version upgrades, with the required migrations applied and the full test/build matrix verified.
Gems
…plus all remaining minor/patch bumps (bootsnap, faraday, rspec-rails, js-routes, bullet, factory_bot, selenium-webdriver, etc.).
railswas already at the latest 8.1.x.npm
Migrations / code changes
config/initializers/inertia_rails.rb(serialize the initial page in a<script>element,data-inertiahead attribute, always include the errors hash), and renamed the managed<title inertia>→<title data-inertia>in the app layout. No client API changes were needed (no axios/qs,<Deferred>,router.cancel,hideProgress, or arrow-function layouts in use; clerk 5 keeps the sameClerk::Authenticatable/ proxy surface).baseUrloption from both tsconfigs;pathsresolve relative to each config so the@/*alias is unchanged.Notable decision
eslint-plugin-react/eslint-plugin-importrelease yet (both peer-cap at eslint 9). Forcing eslint 10 would breaknpm run lint. typescript-eslint already supports both eslint 9 and TypeScript 6.Verification (all green)
tsctype-check, eslint, prettier, vitest (5), Vite client + SSR builds,npm audit --audit-level=high(0 vulnerabilities)🤖 Generated with Claude Code
https://claude.ai/code/session_01D4qYdK1vwbg19M2TB2D386
Generated by Claude Code