Feature Request: Additional option for updating containers - multi-select

[begunfx]

Right now we have the option to update individual containers OR "Update All" (by stack). Would be nice to have the option to multi-select several containers and "Update Selected" as an additional middle-ground update option.

[begunfx]

Additional note: It appears that the current behavior has a bit of an issue? If I trigger one container to update, I cannot trigger another container to update until the previous one was completed. Selecting another container update seems to do nothing.

[scttbnsn]

Two items here — one already fixed, one on the roadmap.

Update blocking bug (your follow-up comment): Fixed in RC2. The action tracking was a single global lock (Ref<string | null>) — triggering one update blocked every other container. Changed to per-container tracking (Ref<Set<string>>) so you can trigger concurrent updates on different containers. This shipped in commits 45b6ada8 and 082a8522 and has been live since v1.5.0-rc.2.

Multi-select "Update Selected" (the main feature request): This is on the roadmap for v1.7.0 (Phase 6.1.1). It needs checkbox selection UI, a bulk action toolbar, and confirmation dialogs for partial selections — more infrastructure than the current per-container and per-stack update patterns support. Noted and tracked.

[scttbnsn]

The concurrent-update blocking bug mentioned in the follow-up comment was fixed in rc.2 (per-container lock replaced the single global lock — commits 45b6ada8 and 082a8522), so you can trigger updates on multiple containers in parallel now.

The multi-select "Update Selected" feature with checkbox selection UI and a bulk action toolbar is queued for v1.7.0 (Phase 6.1.1). It's grouped with dependency-aware ordering because the two share the same selection + confirmation dialog infrastructure.