feat: add Register Update dialog to UpdatesDashboard

[bburda]

Summary

Adds a Register Update button to the Software Updates dashboard toolbar, opening a dialog that POSTs to SOVD /updates. Closes #69.

The dialog collects id (required), update_name (defaults to id when blank), automated (checkbox), and free-form JSON additional metadata. Client-side validates required id and JSON parse; merges metadata extras into the request body before submitting. A new registerUpdate Zustand store action handles the HTTP call.

Generic by design: no vendor-specific fields at the top level - all vendor extras go through the JSON metadata field, so the same dialog works for Uptane, Mender, and any other UpdateProvider plugin.

---

Issue

• closes Add Register Update dialog to UpdatesDashboard #69

---

Type

• Bug fix
• New feature
• Breaking change
• Documentation only

---

Testing

• New unit tests in src/components/RegisterUpdateDialog.test.tsx (4 cases: render, required id, JSON parse, merged body submit).
• Existing UpdatesDashboard.test.tsx suite (11 tests) passes - new toolbar button does not disturb existing behavior.
• Local typecheck (npm run typecheck) clean.

---

Checklist

• Linting passes (npm run lint)
• Build succeeds (npm run build)
• No behavior / API changes that need doc updates (new UI component, additive)

---

Base branch

This PR targets fix/uds-data-tab-rendering (PR #68) rather than main, so it stacks on top of that Data-tab hardening work. Rebase onto main is trivial once #68 merges.

[Copilot]

Pull request overview

Adds a “Register Update” entry point to the Software Updates dashboard so operators can create new updates via POST /updates from the UI, backed by a new Zustand store action.

Changes:

• Added registerUpdate action to the Zustand store to POST update registration payloads.
• Added RegisterUpdateDialog component and wired it into UpdatesDashboard via a new toolbar button.
• Added new Label/Checkbox UI primitives and unit tests for the dialog.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
src/lib/store.ts	Adds registerUpdate store action calling client.POST('/updates', …)
src/components/UpdatesDashboard.tsx	Adds “Register Update” button and renders the dialog
src/components/RegisterUpdateDialog.tsx	Implements the registration dialog UI, validation, and payload construction
src/components/RegisterUpdateDialog.test.tsx	Adds unit tests for dialog validation and submission behavior
src/components/ui/label.tsx	Introduces a Label primitive used by the dialog
src/components/ui/checkbox.tsx	Introduces a Checkbox primitive used by the dialog

[Copilot]

Pull request overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated 2 comments.

Comments suppressed due to low confidence (1)

src/components/UpdatesDashboard.tsx:65

• handleRegister performs a mutation but doesn’t use the existing actionAbortRef cancellation pattern used by prepare/execute/automated/delete. If the dashboard unmounts while a register request is in-flight, it can still call toast.* and refresh() afterward (the comment on lines 57-59 suggests the intent is to avoid stale toasts/state updates on unmounted components). Consider extending registerUpdate to accept an optional AbortSignal and wiring actionAbortRef.current?.signal through, with the same signal.aborted/AbortError guards used in handleAction.

    const handleRegister = async (body: { id: string; [key: string]: unknown }) => {
        try {
            await registerUpdate(body);
            toast.success(`Registered ${body.id}`);
            refresh();
        } catch (e) {
            const msg = e instanceof Error ? e.message : String(e);
            toast.error(`Register failed: ${msg}`);
            throw e;
        }
    };

    // AbortController for mutation actions (prepare/execute/automated/delete).
    // Aborted on unmount so in-flight requests don't resolve into setBusyIds
    // on an unmounted component or issue stale toast notifications.
    const actionAbortRef = useRef<AbortController | null>(null);
    useEffect(() => {
        const controller = new AbortController();
        actionAbortRef.current = controller;
        return () => controller.abort();
    }, []);

[Copilot]

Pull request overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated 2 comments.