Skip to content

feat(gateway): expose version in /api/status and display it in sidebar footer#6367

Open
ilteoood wants to merge 2 commits intozeroclaw-labs:masterfrom
ilteoood:copilot/add-functionality-for-issue-6366
Open

feat(gateway): expose version in /api/status and display it in sidebar footer#6367
ilteoood wants to merge 2 commits intozeroclaw-labs:masterfrom
ilteoood:copilot/add-functionality-for-issue-6366

Conversation

@ilteoood
Copy link
Copy Markdown
Contributor

@ilteoood ilteoood commented May 4, 2026

Summary

  • Base branch: master (all contributions)
  • What changed and why:
    • GET /api/status now includes "version": "<semver>" sourced from env!("CARGO_PKG_VERSION") β€” zero runtime cost, always in sync with the workspace version
    • StatusResponse TS type gains version?: string to match
    • SidebarFooter fetches status on mount and renders v{version} beneath "ZeroClaw Gateway" in both desktop and mobile layouts; fetch failure is silently swallowed (version is cosmetic, same pattern as pairing code fetch in App.tsx)
  • Scope boundary: No other API fields touched; no new endpoint; no config surface
  • Blast radius: Any consumer of /api/status gains a new optional field β€” purely additive
  • Linked issue(s): Closes [Feature]: display ZeroClaw version on the web pageΒ #6366

Validation Evidence (required)

  • Commands run and tail output:
cargo test        β†’ exit 0
cargo fmt --all -- --check        β†’ exit 0
cargo clippy -p zeroclaw-gateway  β†’ Finished `dev` profile [unoptimized + debuginfo] target(s) in 2m 06s
npm run build (web/)              β†’ βœ“ built in 2.26s
  • Beyond CI β€” what did you manually verify?
    The outcome of the change
image
  • If any command was intentionally skipped, why: cargo test / cargo clippy --all-targets skipped β€” full workspace compile exceeds sandbox time budget; gateway-scoped clippy is clean

Security & Privacy Impact (required)

  • New permissions, capabilities, or file system access scope? No
  • New external network calls? No β€” the sidebar calls the existing authenticated /api/status endpoint it already depends on
  • Secrets / tokens / credentials handling changed? No
  • PII, real identities, or personal data in diff, tests, fixtures, or docs? No

Compatibility (required)

  • Backward compatible? Yes β€” version is a new additive field; existing consumers ignoring unknown keys are unaffected
  • Config / env / CLI surface changed? No

Rollback (required for risk: medium and risk: high)

git revert <sha> is the plan.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature]: display ZeroClaw version on the web page

2 participants