Smartgift-AI/AgentHub
14
0
Fork 0
Code Issues 3 Pull Requests Actions Packages Projects Releases 86 Wiki Activity

feat(updates): detect the newest release and self-apply it, including plugin installs

Browse Source 
Update detection was a commit count against the default branch, which says nothing about whether a *version* shipped and is pure noise on the plugin cache (a depth-1 clone, where every distance is a graft artefact). It now reads the forge's own releases API and compares the published tag to this install's package.json version, falling back to the commit count only when no release can be read — with the reason in release_check, so "up to date" never silently means "we could not look".

Two states a commit count cannot express: dev_build (ahead of the newest release, missing nothing from it) now reads "Dev build - N ahead" instead of a false "Up to date"; and on a shallow clone every commits_*_release field is null and dev_build is never asserted, because the numbers would be meaningless.

POST /api/updates/apply gains a second mode, chosen by install kind and never by the request body. A checkout still fast-forwards onto the release tag, rebuilds and self-restarts. A ~/.claude/plugins/cache/ install is refused by applyUpdate (that directory is Claude Code's to replace) and handed instead to a detached chain: claude plugin marketplace update -> claude plugin update -y -> plugin-bootstrap.js --force from the NEW cache dir, which retires this server and starts its replacement. Both write the HTTP response before anything stops the process.

The chain records every outcome to plugin-update.json in the runtime dir, outside the cache the update replaces, so the next server reports it as last_plugin_update: a failed chain is otherwise indistinguishable from a slow one, and the tab would poll a server that never returns. /reload-plugins is deliberately not in the chain - it is REPL-scoped to the session that runs it, so no background process can perform it, and plugin-bootstrap derives PLUGIN_ROOT from its own __dirname, which is what makes it unnecessary for the dashboard.

Also rebrands the sidebar subtitle, splash and page title to SmartGift Solution, and corrects three ARCHITECTURE.md statements that claimed /apply did not exist.

Verified: server 1683/1683, client 486/486, build, prettier, file-header audit, openapi.yaml regenerated.
This commit is contained in:
nntrivi2001
2026-09-10 16:03:07 +07:00
parent eb63569324
commit cc85e35439
23 changed files with 1712 additions and 92 deletions
Download Patch File Download Diff File Expand all files Collapse all files
client/src/lib/types.ts
+97 -5
View File
@@ -1255,6 +1255,8 @@ export interface UpdateStatusPayload {
* shape (e.g. show "Restart after running" only when the command
* actually rewrites the working tree). */
situation?:
| "plugin_managed"
| "release_available"
| "tracking_canonical"
| "fork_or_diverged_tracking"
| "feature_branch"
@@ -1285,9 +1287,79 @@ export interface UpdateStatusPayload {
* restart itself). Absent from `status`/`check` responses. */
applied?: boolean;
/** Set alongside `applied: false` on an `/apply` response that declined to
* act - `"up_to_date"` or `"not_fast_forwardable"` (feature branch /
* detached HEAD, where there's no safe automatic move). */
reason?: "up_to_date" | "not_fast_forwardable";
* act - `"up_to_date"`, `"not_fast_forwardable"` (feature branch /
* detached HEAD, where there's no safe automatic move), or
* `"plugin_managed"` (the install lives in the Claude Code plugin cache,
* which only `/reload-plugins` can swap - the server must not touch it). */
reason?: "up_to_date" | "not_fast_forwardable" | "plugin_managed";
// ── Release layer ──
/** How this copy was installed. `"plugin"` means it runs out of
* `~/.claude/plugins/cache/`, where self-update is refused. */
install_kind?: "plugin" | "checkout";
/** Marketplace the plugin came from (e.g. `"sg"`), parsed from the cache
* path. null for a checkout install. Used to print the exact
* `claude plugin update <plugin>@<marketplace>` command. */
plugin_marketplace?: string | null;
/** Version this install declares in its own package.json, e.g. `"1.5.0"`.
* Compared against `latest_release` to decide `update_available`. */
local_version?: string | null;
/** True for a `--depth` clone, where every commit-distance field is
* meaningless and therefore null - the UI must not render an
* "N commits behind" badge. The Claude Code plugin cache is one. */
shallow_clone?: boolean;
/** `"ok"`, or why the release lookup produced nothing: `"no_remote"`,
* `"remote_not_http"`, `"no_releases"`, `"unreachable"`, `"bad_payload"`,
* or `"http_<status>"`. Anything but `"ok"` means detection fell back to
* the commit-count comparison. */
release_check?: string;
/** Tag of the newest published release, e.g. `"v1.5.0"`. null when
* `release_check !== "ok"`. */
latest_release?: string | null;
/** Human title of that release, when the forge has one. */
latest_release_name?: string | null;
/** Browser URL of the release page, for a "view release notes" link. */
latest_release_url?: string | null;
/** ISO timestamp the release was published. */
latest_release_published_at?: string | null;
/** Release body/changelog, truncated server-side to 4000 chars. */
latest_release_notes?: string | null;
/** Commit the release tag resolves to locally; null when the tag hasn't
* been fetched yet. */
release_sha?: string | null;
/** Commits in the release that this install lacks. null on a shallow
* clone (see `shallow_clone`). */
commits_behind_release?: number | null;
/** Commits this install carries that the release does not. null on a
* shallow clone. Drives the "dev build" label. */
commits_ahead_of_release?: number | null;
/** True when this install is strictly ahead of the newest release and
* missing nothing from it - a build off the branch, not a shipped
* version. Never true at the same time as `update_available`. */
dev_build?: boolean;
/** Plugin name parsed from the cache path (e.g. `"agenthub"`). null for a
* checkout install. Combined with `plugin_marketplace` it forms the
* `claude plugin update <plugin>@<marketplace>` target. */
plugin_name?: string | null;
/** Present only on an `/apply` response. `"plugin"` means the detached
* plugin chain took the job (minutes, and the old server stays up while it
* installs); absent means an in-place git fast-forward + restart. */
mode?: "plugin";
/** Runtime directory the plugin chain writes its log/verdict into. Present
* only on an `/apply` response with `mode: "plugin"`. */
runtime_dir?: string;
/** Verdict of the most recent plugin-update chain, or null when there has
* never been one. `ok: false` is the ONLY way a failed chain becomes
* visible - the server that would have reported it is the one that never
* came back. Read on every status poll for a plugin install. */
last_plugin_update?: {
ok: boolean;
step: string;
error?: string;
note?: string;
plugin_root?: string;
finished_at?: string;
} | null;
}
// ───── Terminal run status ─────
@@ -1316,8 +1388,28 @@ export interface CcConfigChangedPayload {
/** Whether the dashboard itself made the write, or an fs watcher observed
* an external change (e.g. the user editing a file directly). */
source: "dashboard" | "fs";
/** Mutation kind; absent for some fs-watcher events that only report scope. */
action?: "write" | "delete";
/** Mutation kind; absent for some fs-watcher events that only report scope.
* Covers the file editor (`write`/`delete`), settings (`patch`), the
* `claude plugin …` routes
* (`install`/`enable`/`disable`/`update`/`uninstall` for a plugin,
* `add`/`remove`/`update` for a marketplace) and the auth profiles
* (`save`/`rename`/`activate`/`delete`). Keep in step with the `emitChanged`
* call sites in `server/routes/cc-config.js` — the union was previously just
* `write | delete`, which every plugin route already contradicted. */
action?:
| "write"
| "delete"
| "patch"
| "install"
| "enable"
| "disable"
| "update"
| "uninstall"
| "add"
| "remove"
| "save"
| "rename"
| "activate";
/** "user" (~/.claude) or "project" (repo's .claude) config root affected.
* Lets a listening tab decide whether the change is relevant to its view. */
scope?: "user" | "project";