chore(deps): update dependency typescript-eslint to v8.57.0 #26
Reference in New Issue
Block a user
Delete Branch "renovate/typescript-eslint-8.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?
This PR contains the following updates:
8.56.0→8.57.0Release Notes
typescript-eslint/typescript-eslint (typescript-eslint)
v8.57.0Compare Source
This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.56.1Compare Source
This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
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.
This PR has been generated by Renovate Bot.
⏳ CI is still pending — this PR was not merged. Please re-check once the build completes. (Requested via #28)
@judas check again
CI è in failure. Il build sta fallendo — vale la pena controllare i log su Drone prima di procedere con il merge: https://drone.beatrice.wtf/panic.haus/web-ui/156
Il diff in sé è corretto (aggiornamento di tutti i pacchetti
@typescript-eslintda8.56.0a8.57.0, inclusa la pulizia diminimatch@^9.0.5ora sostituita da^10.2.2), ma il CI deve passare prima di poter procedere.cb6d676751to4c1ef49860Analisi del fallimento CI
Il test
DatePicker > opens popup from icon button and closes with Escapeva in timeout nel Drone build #158, ma il problema non è correlato a typescript-eslint v8.57.0.Root cause
Il file
vitest.config.tsnon ha configuratotestTimeout, quindi utilizza il default di 5000ms. In CI, il test DatePicker supera questo limite.Soluzione
Aggiungi
testTimeout: 10000nella sezionetestdivitest.config.ts:Una volta applicato il fix su main, questa PR dovrebbe passare il CI.
Nota: È un problema pre-esistente, non introdotto da questo aggiornamento di dipendenze.