panic.haus/web-ui
1
0
Fork 0
Code Issues 1 Pull Requests 7 Actions Packages Projects Releases Activity

chore(deps): update dependency @storybook/react-vite to v10.2.19 #36

Open
renovate wants to merge 1 commits from renovate/storybook-react-vite-10.x-lockfile into main
pull from: renovate/storybook-react-vite-10.x-lockfile
merge into: panic.haus:main
Conversation 5 Commits 1 Files Changed 1 +33 -63
renovate commented 2026-03-14 07:13:46 +01:00
Collaborator
Copy Link

This PR contains the following updates:

Package Type Update Change
@storybook/react-vite (source) devDependencies patch 10.2.17 → 10.2.19

Release Notes

storybookjs/storybook (@​storybook/react-vite)

v10.2.19

Compare Source

v10.2.18

Compare Source

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [@storybook/react-vite](https://github.com/storybookjs/storybook/tree/next/code/frameworks/react-vite) ([source](https://github.com/storybookjs/storybook/tree/HEAD/code/frameworks/react-vite)) | devDependencies | patch | [`10.2.17` → `10.2.19`](https://renovatebot.com/diffs/npm/@storybook%2freact-vite/10.2.17/10.2.19) | --- ### Release Notes <details> <summary>storybookjs/storybook (@&#8203;storybook/react-vite)</summary> ### [`v10.2.19`](https://github.com/storybookjs/storybook/blob/HEAD/CHANGELOG.md#10219) [Compare Source](https://github.com/storybookjs/storybook/compare/v10.2.18...v10.2.19) - Maintenance: Support vite-plugin-svelte\@&#8203;7 which supports Vite 8 - [#&#8203;34115](https://github.com/storybookjs/storybook/pull/34115), thanks [@&#8203;valentinpalkovic](https://github.com/valentinpalkovic)! - Vite: Support Vite 8 - [#&#8203;33788](https://github.com/storybookjs/storybook/pull/33788), thanks [@&#8203;valentinpalkovic](https://github.com/valentinpalkovic)! ### [`v10.2.18`](https://github.com/storybookjs/storybook/blob/HEAD/CHANGELOG.md#10218) [Compare Source](https://github.com/storybookjs/storybook/compare/v10.2.17...v10.2.18) - Core: Correctly fallback to first detected vitest config file - [#&#8203;33865](https://github.com/storybookjs/storybook/pull/33865), thanks [@&#8203;yannbf](https://github.com/yannbf)! - Core: Fix error reporting in ManagerErrorBoundary - [#&#8203;33915](https://github.com/storybookjs/storybook/pull/33915), thanks [@&#8203;ghengeveld](https://github.com/ghengeveld)! </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My43My4xIiwidXBkYXRlZEluVmVyIjoiNDMuNzUuMCIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOltdfQ==-->
renovate changed title from chore(deps): update dependency @storybook/react-vite to v10.2.18 to chore(deps): update dependency @storybook/react-vite to v10.2.19 2026-03-14 23:12:51 +01:00
judas commented 2026-03-15 04:35:44 +01:00
Collaborator
Copy Link

⚠️ Merge Failed — Server Error

CI was passing for this PR, but the Gitea API returned a persistent 405 – Please try again later error when attempting to merge. The branch has not been merged or deleted.

Please merge this manually or retry later.

## ⚠️ Merge Failed — Server Error CI was **passing** for this PR, but the Gitea API returned a persistent `405 – Please try again later` error when attempting to merge. The branch has **not** been merged or deleted. Please merge this manually or retry later.
bea commented 2026-03-15 04:38:11 +01:00
Owner
Copy Link

@judas retry

@judas retry
👀 1
judas approved these changes 2026-03-15 04:38:42 +01:00
judas left a comment
Collaborator
Copy Link

Aggiornamento di routine del lockfile per @storybook/react-vite da 10.2.17 → 10.2.19. Le modifiche sono interamente in yarn.lock e consistono in:

  • Bump di @storybook/react-vite, @storybook/builder-vite, @storybook/csf-plugin, @storybook/react, @storybook/react-dom-shim a 10.2.19
  • Rimozione di dipendenze non più necessarie: rolldown@1.0.0-rc.9 e tutti i relativi binding platform-specifici, lightningcss@1.32.0 e binding, @emnapi/*, @napi-rs/wasm-runtime, @oxc-project/*, @tybys/wasm-util, detect-libc, std-env@3.10.0
  • Aggiornamenti minori di altre dipendenze: react-docgen 8.0.2→8.0.3, ast-v8-to-istanbul 0.3.11→1.0.0, baseline-browser-mapping, caniuse-lite, electron-to-chromium, magicast, lru-cache

✅ CI verde. Le modifiche sono coerenti con un bump di patch/minor di Storybook e non introducono nulla di inaspettato. Il lockfile appare corretto.

⚠️ Il PR risulta attualmente non mergeable (probabilmente conflitti con main). Potrebbe essere necessario aggiornare il branch prima del merge.

Aggiornamento di routine del lockfile per `@storybook/react-vite` da `10.2.17` → `10.2.19`. Le modifiche sono interamente in `yarn.lock` e consistono in: - Bump di `@storybook/react-vite`, `@storybook/builder-vite`, `@storybook/csf-plugin`, `@storybook/react`, `@storybook/react-dom-shim` a `10.2.19` - Rimozione di dipendenze non più necessarie: `rolldown@1.0.0-rc.9` e tutti i relativi binding platform-specifici, `lightningcss@1.32.0` e binding, `@emnapi/*`, `@napi-rs/wasm-runtime`, `@oxc-project/*`, `@tybys/wasm-util`, `detect-libc`, `std-env@3.10.0` - Aggiornamenti minori di altre dipendenze: `react-docgen` 8.0.2→8.0.3, `ast-v8-to-istanbul` 0.3.11→1.0.0, `baseline-browser-mapping`, `caniuse-lite`, `electron-to-chromium`, `magicast`, `lru-cache` ✅ CI verde. Le modifiche sono coerenti con un bump di patch/minor di Storybook e non introducono nulla di inaspettato. Il lockfile appare corretto. > ⚠️ Il PR risulta attualmente **non mergeable** (probabilmente conflitti con `main`). Potrebbe essere necessario aggiornare il branch prima del merge.
bea commented 2026-03-15 04:39:16 +01:00
Owner
Copy Link

@judas puoi risolvere il conflitto di lockfile?

@judas puoi risolvere il conflitto di lockfile?
👀 1
judas commented 2026-03-15 04:39:44 +01:00
Collaborator
Copy Link

C'è un conflitto vero e proprio nel yarn.lock che non può essere risolto automaticamente con un merge. Questo succede perché entrambi i branch hanno modificato le stesse righe del lockfile.

Purtroppo non posso modificare direttamente i file nel repository tramite gli strumenti a mia disposizione. Per risolvere il conflitto manualmente devi:

# Checkout del branch della PR
git fetch origin
git checkout renovate/storybook-react-vite-10.x-lockfile

# Merge di main nel branch
git merge origin/main

# Risolvi il conflitto nel yarn.lock accettando entrambe le versioni
# (oppure rigeneralo da zero)
rm yarn.lock
yarn install

# Commit e push
git add yarn.lock
git commit -m "fix: resolve yarn.lock conflict"
git push origin renovate/storybook-react-vite-10.x-lockfile

Il modo più pulito è cancellare il yarn.lock e rigenerarlo con yarn install — in questo modo yarn risolve tutto da solo senza conflitti manuali. Dopo il push il PR tornerà mergeable.

C'è un conflitto vero e proprio nel `yarn.lock` che non può essere risolto automaticamente con un merge. Questo succede perché entrambi i branch hanno modificato le stesse righe del lockfile. Purtroppo **non posso modificare direttamente i file nel repository** tramite gli strumenti a mia disposizione. Per risolvere il conflitto manualmente devi: ```bash # Checkout del branch della PR git fetch origin git checkout renovate/storybook-react-vite-10.x-lockfile # Merge di main nel branch git merge origin/main # Risolvi il conflitto nel yarn.lock accettando entrambe le versioni # (oppure rigeneralo da zero) rm yarn.lock yarn install # Commit e push git add yarn.lock git commit -m "fix: resolve yarn.lock conflict" git push origin renovate/storybook-react-vite-10.x-lockfile ``` Il modo più pulito è cancellare il `yarn.lock` e rigenerarlo con `yarn install` — in questo modo yarn risolve tutto da solo senza conflitti manuali. Dopo il push il PR tornerà mergeable.
renovate added 1 commit 2026-03-18 07:12:31 +01:00
chore(deps): update dependency @storybook/react-vite to v10.2.19
All checks were successful
continuous-integration/drone/pr Build is passing
Details
398c059b2c
renovate force-pushed renovate/storybook-react-vite-10.x-lockfile from 4776adbc59 to 398c059b2c 2026-03-18 07:12:31 +01:00 Compare
All checks were successful
continuous-integration/drone/pr Build is passing
Details
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin renovate/storybook-react-vite-10.x-lockfile:renovate/storybook-react-vite-10.x-lockfile
git checkout renovate/storybook-react-vite-10.x-lockfile
Sign in to join this conversation.
Reviewers
No Reviewers
judas
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
bea judas renovate
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: panic.haus/web-ui#36
Delete Branch "renovate/storybook-react-vite-10.x-lockfile"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?