chore(deps): update all non-major dependencies#24
Conversation
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
3fc086d to
088cc4f
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
7 times, most recently
from
0f994e9 to
2e635ea
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
14 times, most recently
from
be3d4d4 to
d855450
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
7 times, most recently
from
2a90a19 to
8b98fa7
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
15 times, most recently
from
bf2687f to
18f7e72
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
12 times, most recently
from
ba5e9e3 to
a0686bf
Compare
📝 WalkthroughWalkthroughBumped PHP constraint ( Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related issues
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (2)
composer.json (1)
20-25: Verify laravel/pail compatibility with dev scripts.The composer.json scripts actively use
php artisan pail --timeout=0in both "dev" (line 58) and "dev:ssr" (line 63) scripts. While laravel/sail is listed as a require-dev dependency, no active Docker Compose configuration was found in the repository root. The pail version update (^1.2.3 → ^1.2.6) should be tested with the existing scripts to ensure the--timeout=0flag continues to work as expected. If you're using Sail locally, verify the docker-compose configuration after the sail update (1.47.0 → 1.56.0) since it spans 9 patch versions and may introduce environment or CLI changes.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@composer.json` around lines 20 - 25, composer.json upgrades to laravel/pail and laravel/sail may break the dev scripts that call "php artisan pail --timeout=0" (scripts "dev" and "dev:ssr"); reproduce the dev workflow locally and run both scripts to confirm the --timeout=0 flag still works with laravel/pail ^1.2.6, and if using Sail run the same inside Sail (or with your docker-compose) to ensure CLI/compose compatibility after sail ^1.56.0; if failures occur, either pin laravel/pail to the previous working version or adjust the scripts to the new pail CLI options, and update any docker-compose/sail configuration to match the new sail behavior.package.json (1)
51-51: Test pnpm package manager upgrade across environments before merging.The upgrade from pnpm 10.21.0 to 10.33.0 spans multiple semi-breaking changes that warrant verification:
- v10.26.0: Integrity hashes added for HTTP tarball dependencies (may alter lockfile)
- v10.27.0: Global store layout changed for unscoped packages
- v10.33.0: When using CI with
--frozen-lockfile, pnpm now strictly fails on incompatible lockfiles (instead of silently falling back)The lockfile version 9.0 is compatible with pnpm 10.33.0, but regenerate the lockfile and test across all environments (CI with frozen-lockfile mode, local development) to ensure these changes don't cause installation failures.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@package.json` at line 51, The package.json packageManager field was bumped to "pnpm@10.33.0" which may introduce lockfile and store layout changes; regenerate the pnpm lockfile with pnpm@10.33.0 (or the target CI image) and commit the updated lockfile, then run installs in all environments referenced in CI and local development (including CI with --frozen-lockfile) to ensure no failures from integrity/hash or store-layout changes; if issues appear, either pin to a compatible pnpm version in packageManager or apply the required lockfile/store migrations and document the change.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@package.json`:
- Around line 28-38: The `@nuxt/ui` plugin option `inertia: true` is outdated; in
your Vite config replace it with the new API by changing the plugin invocation
that references Nuxt UI (look for nuxtUi or `@nuxt/ui` usage inside
vite.config.ts, e.g., a call like nuxtUi({...}) or in the plugins array) to use
router: 'inertia' instead of inertia: true so the options object becomes router:
'inertia'.
---
Nitpick comments:
In `@composer.json`:
- Around line 20-25: composer.json upgrades to laravel/pail and laravel/sail may
break the dev scripts that call "php artisan pail --timeout=0" (scripts "dev"
and "dev:ssr"); reproduce the dev workflow locally and run both scripts to
confirm the --timeout=0 flag still works with laravel/pail ^1.2.6, and if using
Sail run the same inside Sail (or with your docker-compose) to ensure
CLI/compose compatibility after sail ^1.56.0; if failures occur, either pin
laravel/pail to the previous working version or adjust the scripts to the new
pail CLI options, and update any docker-compose/sail configuration to match the
new sail behavior.
In `@package.json`:
- Line 51: The package.json packageManager field was bumped to "pnpm@10.33.0"
which may introduce lockfile and store layout changes; regenerate the pnpm
lockfile with pnpm@10.33.0 (or the target CI image) and commit the updated
lockfile, then run installs in all environments referenced in CI and local
development (including CI with --frozen-lockfile) to ensure no failures from
integrity/hash or store-layout changes; if issues appear, either pin to a
compatible pnpm version in packageManager or apply the required lockfile/store
migrations and document the change.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 7f2e769f-a6c8-47c3-a5d0-506acb766c36
⛔ Files ignored due to path filters (2)
composer.lockis excluded by!**/*.lockpnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (2)
composer.jsonpackage.json
| "@inertiajs/vue3": "^2.3.21", | ||
| "@nuxt/ui": "^4.6.1", | ||
| "@vitejs/plugin-vue": "^6.0.5", | ||
| "@vueuse/core": "^14.2.1", | ||
| "clsx": "^2.1.1", | ||
| "concurrently": "^9.2.1", | ||
| "laravel-vite-plugin": "^2.0.1", | ||
| "laravel-vite-plugin": "^2.1.0", | ||
| "typescript": "^5.9.3", | ||
| "vite": "^7.2.2", | ||
| "vue": "^3.5.24", | ||
| "ziggy-js": "^2.6.0" | ||
| "vue": "^3.5.32", | ||
| "ziggy-js": "^2.6.2" |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Description: Verify Vite configuration APIs are compatible with updated versions
# Display the vite.config.ts file to review plugin usage
cat vite.config.ts
# Check for Inertia usage patterns in Vue components
rg -nP "import.*@inertiajs/vue3" --type=ts --type=vue -C2
# Verify `@nuxt/ui` plugin usage with inertia option
rg -nP "ui\(\{" vite.config.ts -A10Repository: nuxt-ui-templates/starter-laravel
Length of output: 1263
🌐 Web query:
@nuxt/ui 4.6.1 release notes inertia option
💡 Result:
@nuxt/ui v4.6.1 release notes (re: Inertia)
Nuxt UI v4.6.1 (released 2026-04-03) is a bugfix-only release and does not mention any Inertia-specific change in its release notes. The listed fixes are around AI streaming detection, Chat components, DashboardSidebar, Modal/Slideover/Drawer warnings, and module/Vite-related fixes. [1]
“Inertia option” (how to enable Inertia)
In the current Nuxt UI Vite plugin docs, Inertia support is enabled via:
ui({
router: 'inertia'
})—not inertia: true. [2]
Sources: [1] [2]
🌐 Web query:
laravel-vite-plugin 2.1.0 changelog breaking changes
💡 Result:
laravel-vite-plugin v2.1.0 (released Jan 20, 2026) — what changed
Release notes list two changes: (github.com)
- Changelog/docs fix: “missing 2.0.0 release notes in changelog” (documentation-only). (github.com)
- CORS allowed-origins implementation change: the plugin now uses Vite’s exported default allowed-origins pattern (instead of a locally-copied regex) to “future-proof” against upstream pattern changes; related tests were tightened to ensure all expected hosts match. (github.com)
Breaking changes?
- No explicit breaking changes are called out in the v2.1.0 release notes. (github.com)
- Practically, the only potential behavior change is around the dev-server CORS origin matching defaults (if you relied on quirks of the previously copied regex). (github.com)
Citations:
- 1: https://github.com/laravel/vite-plugin/releases
- 2: https://github.com/laravel/vite-plugin/releases
- 3: https://github.com/laravel/vite-plugin/releases
- 4: https://github.com/laravel/vite-plugin/releases
- 5: [2.x] Use vite export to future proof additional pattern changes laravel/vite-plugin#339
🌐 Web query:
@vitejs/plugin-vue 6.0.5 transformAssetUrls API
💡 Result:
In @vitejs/plugin-vue 6.0.5, transformAssetUrls is configured under the plugin’s template option and is passed through to @vue/compiler-sfc’s SFCTemplateCompileOptions.transformAssetUrls. By default, the plugin rewrites certain static asset attributes (e.g. <img src="../x.png">) into ESM imports, and you can customize/disable that behavior via template.transformAssetUrls. [1]
Where to configure
// vite.config.ts
import vue from '@vitejs/plugin-vue'
export default {
plugins: [
vue({
template: {
transformAssetUrls: /* ... */
}
})
]
}[1]
API / types
template.transformAssetUrls accepts: boolean | AssetURLTagConfig | AssetURLOptions. [2]
false/true: disable / enable the transform. [2]AssetURLTagConfig:{ [tag: string]: string[] }mapping tags to attributes to rewrite. [2]AssetURLOptions:base?: string | nullincludeAbsolute?: booleantags?: AssetURLTagConfig
[2]
Default tag/attribute transforms (plugin default)
{
video: ['src', 'poster'],
source: ['src'],
img: ['src'],
image: ['xlink:href', 'href'],
use: ['xlink:href', 'href']
}[1]
Sources: @vitejs/plugin-vue README (asset URL handling + default tags) [1]; @vue/compiler-sfc type definitions for transformAssetUrls / AssetURLOptions [2].
🌐 Web query:
@inertiajs/vue3 2.3.21 breaking changes
💡 Result:
@inertiajs/vue3 v2.3.21 does not introduce any documented breaking changes. The upstream Inertia v2.3.21 release notes list only maintenance updates:
- Bump lodash-es from 4.17.3 → 4.18.1 [1]
- Bump Vite (repo/dev tooling) [1]
- Improve Playwright CI cache (CI-only) [1]
So if you’re upgrading from v2.3.20 → v2.3.21, you generally shouldn’t need any code changes—just run your usual test/build to confirm no dependency/tooling side-effects. [1], [2]
Sources: [1] [2]
Update @nuxt/ui plugin configuration: change inertia: true to router: 'inertia'.
The upgrade to @nuxt/ui v4.6.1 changes the Inertia integration API. The vite.config.ts currently uses the outdated inertia: true option, but the current version requires router: 'inertia':
vite.config.ts fix
ui({
- inertia: true,
+ router: 'inertia',
components: {
dirs: ['resources/js/components'],
},
ui: {
colors: {
primary: 'scarlet',
neutral: 'neutral',
},
},
}),Other package updates (@vitejs/plugin-vue, laravel-vite-plugin, @inertiajs/vue3) have no API-breaking changes and are compatible with their current usage patterns.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@package.json` around lines 28 - 38, The `@nuxt/ui` plugin option `inertia:
true` is outdated; in your Vite config replace it with the new API by changing
the plugin invocation that references Nuxt UI (look for nuxtUi or `@nuxt/ui` usage
inside vite.config.ts, e.g., a call like nuxtUi({...}) or in the plugins array)
to use router: 'inertia' instead of inertia: true so the options object becomes
router: 'inertia'.
This PR contains the following updates:
^9.39.1→^9.39.4^2.2.15→^2.3.21^4.1.0→^4.6.14.53.1→4.60.1^4.1.17→^4.2.2^24.10.0→^24.12.2^6.0.1→^6.0.5^14.6.0→^14.7.0^14.1.0→^14.2.1^9.39.1→^9.39.4^10.5.1→^10.8.0^2.0.10→^2.0.24^2.0.1→^2.1.0^12.37.0→^12.56.0^1.2.3→^1.2.6^1.25.1→^1.29.0^1.47.0→^1.56.0^2.10.1→^2.11.1^1.30.2→^1.32.0^8.8.2→^8.9.3^3.8.4→^3.8.6^8.4.14→^8.5.510.21.0→10.33.0^3.6.2→^3.8.2^0.7.1→^0.7.2^2.6.0→^2.6.2^8.46.3→^8.58.1^3.5.24→^3.5.32^3.1.3→^3.2.6^2.6.0→^2.6.2Release Notes
eslint/eslint (@eslint/js)
v9.39.4Compare Source
v9.39.3Compare Source
Bug Fixes
791bf8dfix: restore TypeScript 4.0 compatibility in types (#20504) (sethamus)Chores
8594a43chore: upgrade @eslint/js@9.39.3 (#20529) (Milos Djermanovic)9ceef92chore: package.json update for @eslint/js release (Jenkins)af498c6chore: ignore/docs/v9.xin link checker (#20453) (Milos Djermanovic)v9.39.2Compare Source
inertiajs/inertia (@inertiajs/vue3)
v2.3.21Compare Source
What's Changed
New Contributors
Full Changelog: inertiajs/inertia@v2.3.20...v2.3.21
v2.3.18Compare Source
What's Changed
server-rendererdependency from Vue adapter type by @pascalbaljet in #2955New Contributors
Full Changelog: inertiajs/inertia@v2.3.17...v2.3.18
v2.3.17Compare Source
What's Changed
Full Changelog: inertiajs/inertia@v2.3.16...v2.3.17
v2.3.16Compare Source
What's Changed
New Contributors
Full Changelog: inertiajs/inertia@v2.3.15...v2.3.16
v2.3.15Compare Source
What's Changed
history.replaceStateby @pascalbaljet in #2889bfcacherestoration for encrypted history by @pascalbaljet in #2890Full Changelog: inertiajs/inertia@v2.3.14...v2.3.15
v2.3.14Compare Source
What's Changed
useFormtype inference when passing data as callback by @pascalbaljet in #2878Full Changelog: inertiajs/inertia@v2.3.13...v2.3.14
v2.3.13Compare Source
What's Changed
useFormtype inference in generic wrapper components by @pascalbaljet in #2851validate()method by @pascalbaljet in #2854Full Changelog: inertiajs/inertia@v2.3.12...v2.3.13
v2.3.12Compare Source
What's Changed
formTargetattribute in the<Form>component by @pascalbaljet in #2844<Deferred>from rendering children with undefined props by @pascalbaljet in #2846Full Changelog: inertiajs/inertia@v2.3.11...v2.3.12
v2.3.11Compare Source
What's Changed
useForm()keys by @pascalbaljet in #2823useFormwithout arguments by @pascalbaljet in #2830truetoinertattribute in React 19 by @pascalbaljet in #2831Full Changelog: inertiajs/inertia@v2.3.10...v2.3.11
v2.3.10Compare Source
What's Changed
asyncandsyncoptions tocancelAllmethod by @pascalbaljet in #2814<InfiniteScroll>test in WebKit CI by @pascalbaljet in #2818oncePropsas second argument in client-side visit props callback by @pascalbaljet in #2816Full Changelog: inertiajs/inertia@v2.3.9...v2.3.10
v2.3.9Compare Source
What's Changed
New Contributors
Full Changelog: inertiajs/inertia@v2.3.8...v2.3.9
v2.3.8Compare Source
What's Changed
mergeDataIntoQueryString()by @pascalbaljet in #2798<WhenVisible>re-registering observer when params change by @pascalbaljet in #2804New Contributors
Full Changelog: inertiajs/inertia@v2.3.7...v2.3.8
v2.3.7Compare Source
What's Changed
dontRemember()method to form helper by @pascalbaljet in #2792replaceState()when page data has actually changed by @pascalbaljet in #2793@typescript-eslint/unbound-methodwarning when destructuringuseForm()methods by @pascalbaljet in #2794Full Changelog: inertiajs/inertia@v2.3.6...v2.3.7
v2.3.6Compare Source
What's Changed
Full Changelog: inertiajs/inertia@v2.3.5...v2.3.6
v2.3.5Compare Source
What's Changed
hasAnyState()to actually check for browser history by @pascalbaljet in #2785dataandparamsprops in<WhenVisible>by @pascalbaljet in #2789QuotaExceededErrorin WebKit by @pascalbaljet in #2788Full Changelog: inertiajs/inertia@v2.3.4...v2.3.5
v2.3.4Compare Source
What's Changed
Full Changelog: inertiajs/inertia@v2.3.3...v2.3.4
v2.3.3Compare Source
What's Changed
New Contributors
Full Changelog: inertiajs/inertia@v2.3.2...v2.3.3
v2.3.2Compare Source
What's Changed
router.reload()withoutonly/exceptby @pascalbaljet in #2761fetchingin default<WhenVisible>slot by @pascalbaljet in #2766Full Changelog: inertiajs/inertia@v2.3.1...v2.3.2
v2.3.1Compare Source
What's Changed
New Contributors
Full Changelog: inertiajs/inertia@v2.3.0...v2.3.1
v2.3.0Compare Source
What's Changed
useForm()by @pascalbaljet in #2684<Form>component by @pascalbaljet in #2700New Contributors
Full Changelog: inertiajs/inertia@v2.2.21...v2.3.0
v2.2.21Compare Source
What's Changed
viewTransitiontoFormComponentOptionstype by @pascalbaljet in #2741Full Changelog: inertiajs/inertia@v2.2.20...v2.2.21
v2.2.20Compare Source
What's Changed
once()props by @pascalbaljet in #2732New Contributors
Full Changelog: inertiajs/inertia@v2.2.19...v2.2.20
v2.2.19Compare Source
What's Changed
Full Changelog: inertiajs/inertia@v2.2.18...v2.2.19
v2.2.18Compare Source
What's Changed
objectsAreEqual()checks all keys in both objects by @pascalbaljet in #2705Full Changelog: inertiajs/inertia@v2.2.17...v2.2.18
v2.2.17Compare Source
What's Changed
<WhenVisible>loading state after a page reload by @pascalbaljet in #2699indicesarray format when submitting data usingFormDataby @pascalbaljet in #2701Full Changelog: inertiajs/inertia@v2.2.16...v2.2.17
v2.2.16Compare Source
What's Changed
defaultValuein Form component by @pascalbaljet in #2685<Link>withprefetch="click"by @pascalbaljet in #2676useContexttouseinusePage()hook by @HichemTab-tech in #2680formDataToObject()when mixing numeric and non-numeric object keys by @pascalbaljet in #2692InfiniteScrollscroll preservation by @skryukov in #2689Appcomponent by @pascalbaljet in #2695preserveScrollandpreserveStatewhen finding cached response by @pascalbaljet in #2694Full Changelog: inertiajs/inertia@v2.2.15...v2.2.16
nuxt/ui (@nuxt/ui)
v4.6.1Compare Source
Bug Fixes
part.statefor streaming detection and deprecateisReasoningStreaming(d2d7543)collapsed: falsein mobile menu slots (957a0f5), closes #6157reka-uito prevent injection errors (#6286) (b822c43)v4.6.0Compare Source
⚠ BREAKING CHANGES
moduleDependenciesto manipulate options (#5384)Features
filesslot (12d6020)trueValue/falseValueprops (#6150) (91c6356)highlight-variantprop (#5746) (df080ce)filterprop (#6153) (a529b43)fileImageprop (#5935) (40f9c2e)autocompleteprop (#6026) (ee8a248)rangeprop (#6203) (c124f29)moduleDependenciesto manipulate options (#5384) (dd3f5c5)Bug Fixes
liftcalls for unavailable list extensions (#6100) (065db6b)statusandstatusTextproperties (1350d62), closes #6134close:preventemit (#6226) (9a0d501)v4.5.1Compare Source
Bug Fixes
stroke-defaultandfill-bg(#6095) (0e9198e)transformUIfrom mutating cacheduseComponentUIvalue (286738a), closes #6104 #4387Configuration
📅 Schedule: (UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.