chore: update rolldown to 1.1.3

[shulaoda]

See https://github.com/rolldown/rolldown/releases/tag/v1.1.3

[pkg-pr-new]

Open in StackBlitz

@vitejs/plugin-legacy

pnpm add https://pkg.pr.new/@vitejs/plugin-legacy@22763 -D

npm i https://pkg.pr.new/@vitejs/plugin-legacy@22763 -D

yarn add https://pkg.pr.new/@vitejs/plugin-legacy@22763.tgz -D

vite

pnpm add https://pkg.pr.new/vite@22763 -D

npm i https://pkg.pr.new/vite@22763 -D

yarn add https://pkg.pr.new/vite@22763.tgz -D

commit: 9a37c5d

[shulaoda]

/ecosystem-ci run

[vite-ecosystem-ci]

📝 Ran ecosystem CI on 0e21011: Open

suite	result	latest scheduled
astro	❌ failure	❌ failure
react-router	❌ failure	❌ failure
storybook	✅ success	❌ failure
vitest	❌ failure	✅ success
tanstack-start	⏹️ cancelled	⏹️ cancelled

✅ nuxt, laravel, module-federation, marko, sveltekit, qwik, analogjs, quasar, vite-plugin-vue, vike, unocss, vite-environment-examples, vite-plugin-pwa, vuepress, waku, vite-plugin-react, vitepress, vite-setup-catalogue, vite-plugin-cloudflare, vite-plugin-rsc, vite-plugin-svelte

[shulaoda]

/ecosystem-ci run

[vite-ecosystem-ci]

📝 Ran ecosystem CI on 0e21011: Open

suite	result	latest scheduled
astro	❌ failure	❌ failure
react-router	❌ failure	❌ failure
tanstack-start	⏹️ cancelled	⏹️ cancelled
storybook	✅ success	❌ failure

✅ nuxt, analogjs, module-federation, marko, laravel, vite-environment-examples, vite-plugin-svelte, vike, unocss, vite-plugin-pwa, sveltekit, qwik, vite-plugin-react, quasar, vitest, vite-plugin-vue, vuepress, vite-plugin-cloudflare, vitepress, vite-setup-catalogue, waku, vite-plugin-rsc

[sapphi-red]

I think we can start bumping rolldown by renovate instead: #22591

[shulaoda]

I think we can start bumping rolldown by renovate instead: #22591

Nice, I agree. I just want to confirm Vite's release cadence and whether minimumReleaseAge will have any impact?

Also, I used to trigger ecosystem tests by opening a PR. Will switching to renovate[bot] affect that workflow? 🤔

[sapphi-red]

Nice, I agree. I just want to confirm Vite's release cadence and whether minimumReleaseAge will have any impact?

Since Rolldown's version is no longer fixed, whenever you release Rolldown it will land on the end users (unless it's a minor / major).

I used to trigger ecosystem tests by opening a PR. Will switching to renovate[bot] affect that workflow? 🤔

I guess it'd be easier if you trigger the CI from Rolldown repo.

[shulaoda]

Nice, I agree. I just want to confirm Vite's release cadence and whether minimumReleaseAge will have any impact?

Since Rolldown's version is no longer fixed, whenever you release Rolldown it will land on the end users (unless it's a minor / major).

I used to trigger ecosystem tests by opening a PR. Will switching to renovate[bot] affect that workflow? 🤔

I guess it'd be easier if you trigger the CI from Rolldown repo.

Make sense for me