ServerKit is a lightweight, modern server control panel for managing web applications, databases, and services on your VPS or dedicated server. Built with Python/Flask backend and React frontend.
Python astracloudflarecontrol-panelcyberpaneldnsfablehosting-control-panelhosting-panelkimi-k3server-managementserverkitubuntu-web-panelwebserver
feat(sdk): bump to 1.2.0 + PluginSlot/ErrorBoundary exports
Juan Denis798467baba53
diff --git a/backend/app/utils/sdk.py b/backend/app/utils/sdk.pyindex 43c7b506..133b2818 100644--- a/backend/app/utils/sdk.py+++ b/backend/app/utils/sdk.py@@ -27,7 +27,10 @@ import refrom app.utils.version import compare_versions# Keep in lock-step with frontend/src/plugins/sdk/index.js `SDK_VERSION`.-SDK_VERSION = '1.1.0'+# 1.2.0 — plan 52 Phases 4-5: layout/feedback primitives, ui/* form kit,+# common hooks, format utils, and the cross-feature embeds (git repo-connect,+# backups ProtectionPanel) the WordPress runtime-ESM extraction needed.+SDK_VERSION = '1.2.0'def _version_tuple(v):diff --git a/frontend/src/plugins/sdk/index.js b/frontend/src/plugins/sdk/index.jsindex 241c9d20..5058a272 100644--- a/frontend/src/plugins/sdk/index.js+++ b/frontend/src/plugins/sdk/index.js@@ -38,7 +38,7 @@// GET /api/v1/plugins/contributions. The backend mirror lives in// backend/app/utils/sdk.py — keep the two in lock-step (asserted by// backend/tests/test_sdk_contract.py).-export const SDK_VERSION = '1.1.0';+export const SDK_VERSION = '1.2.0';export { api, default as defaultApi } from '../../services/api';@@ -132,6 +132,23 @@ export { useTopbarActions } from '../../hooks/useTopbarActions';export { formatBytes } from '../../utils/formatBytes';export { timeAgo, formatRelativeTime, formatDuration } from '../../utils/time';-// NOTE: additive exports above ship without an SDK_VERSION bump (stays 1.1.0)-// because the backend mirror (backend/app/utils/sdk.py) is frozen by a-// concurrent workstream this phase; bump both in lock-step at Phase 5.+// Generic page furniture + cross-feature embeds (plan 52 Phase 5 — the+// WordPress runtime-ESM extraction proved these out). Two consumer classes:+// - generic primitives any extension page may need (ErrorBoundary,+// DangerZone, ResourceAdvisory, ResourceListPage, the logs drawer, and+// PluginSlot so an extension can itself host a slot);+// - shared cross-feature embeds with ≥2 consumers (a git repo-connect form+// used by both the Git and WordPress surfaces; the backups protection+// panel embedded by both the Backups page and WordPress). Exposing them+// here pins their props as SDK contract — change them accordingly.+export { default as ErrorBoundary, ErrorState } from '../../components/ErrorBoundary';+export { DangerZone } from '../../components/DangerZone';+export { default as ResourceAdvisory } from '../../components/ResourceAdvisory';+export { default as PluginSlot } from '../../components/PluginSlot';+export { default as ResourceListPage } from '../../components/layouts/ResourceListPage';+export { useLogsDrawer } from '../../contexts/LogsDrawerContext';+export { default as RepoConnectForm } from '../../components/git/RepoConnectForm';+export {+ GIT_PROVIDERS, detectProvider, RepoProviderStrip,+} from '../../components/git/GitProviders';+export { default as ProtectionPanel } from '../../components/backups/ProtectionPanel';