Simon Rey 08be405a60 fix(compose): show error step when CLI version fetch fails during onboarding ... When the GitHub API rate limit is hit (or any network error occurs), checkDownloadedCommand now catches the failure, sets a composeVersionCheckFailed context value, and the onboarding flow displays a dedicated error step instead of proceeding with broken placeholder text. Fixes #13868 Signed-off-by: Simon Rey <simon.rey@outlook.com> Co-authored-by: Claude <claude@anthropic.com> Made-with: Cursor Signed-off-by: Simon Rey <51708585+simonrey1@users.noreply.github.com> Made-with: Cursor		2026-04-17 16:07:40 +02:00
..
compose	fix(compose): show error step when CLI version fetch fails during onboarding	2026-04-17 16:07:40 +02:00
docker/packages	chore(deps-dev): bump the vitest group with 2 updates	2026-04-10 10:09:22 +02:00
kind	fix(renderer): hide update button when provider has no installed version	2026-04-16 09:44:16 +02:00
kube-context	chore(deps-dev): bump the vitest group with 2 updates	2026-04-10 10:09:22 +02:00
kubectl-cli	chore(deps-dev): bump the vitest group with 2 updates	2026-04-10 10:09:22 +02:00
lima	chore(deps-dev): bump the vitest group with 2 updates	2026-04-10 10:09:22 +02:00
podman/packages	chore(deps-dev): bump msw from 2.13.3 to 2.13.4	2026-04-17 10:59:43 +02:00
podman-docker-context	chore(deps-dev): bump the vitest group with 2 updates	2026-04-10 10:09:22 +02:00
registries	chore(deps-dev): bump the vitest group with 2 updates	2026-04-10 10:09:22 +02:00
extensions.spec.ts	fix: rename kubectl extension (#5255)	2023-12-14 09:36:45 +01:00
vitest.config.js	refactor(extensions): simplify vitest config (#12103)	2025-04-09 10:42:39 +02:00