Repository navigation
v1.3.0
Changed
-
Both Inertia stacks move to Inertia.js 3 (#25). The versions are chained rather than independent: Inertia 3's React adapter requires React 19, and
@vitejs/plugin-react6 requires Vite 8, so the whole front end moves together.package from to @inertiajs/react, @inertiajs/vue3 ^2.0.0 ^3.9.1 react, react-dom ^18.2.0 ^19.3.1 @vitejs/plugin-react ^4.2.0 ^6.1.2 @vitejs/plugin-vue ^5.0.5 ^6.0.10 typescript ^5.6.3 ^7.0.2 vite ^6.4.4 ^8.3.4 @types/node ^18.13.0 ^26.6.5 vue ^3.4.27 ^3.5.44 vue-tsc ^2.0.21 ^3.3.13 vite-plugin-rails ^0.5.0 ^0.6.0 -
The React entrypoint resolves pages differently. Inertia 3 narrowed its resolver type so that a promise of a module object is no longer accepted, and
resolvePageComponentnow unwrapsdefaultitself and is typed with the exportedResolvedComponent.
Added
- Both Inertia stacks install
config/initializers/inertia_rails.rb. Inertia 3 reads the initial page from a<script type="application/json">element and expects adata-inertiahead attribute;inertia_railssupports both but defaults to the v2 behaviour, so without this the client loads and renders nothing. The initializer also setsalways_include_errors_hash, which becomes the default in InertiaRails 4.0.
Internal
- Dependabot watches bundler, npm and GitHub Actions weekly. Majors are held back for the two stub manifests, since a major there changes the starter kit and needs an install-and-build pass across all three stacks (#20)
- The nightly schedule lives in its own workflow (#19). GitHub disables a workflow carrying a
schedule:trigger after 60 days without repository activity, and disables its other triggers with it — which is how CI came to be switched off for the twelve months before 1.2.0. An idle stretch can now cost only the nightly run, never pull request CI. actions/checkout4 → 7, prettier 3.3.2 → 3.9.10 (#21, #22)
Full Changelog: v1.2.1...v1.3.0