feat: show build identity in About screens#103595
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: aeca34f491
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| ? html`<time | ||
| dir="auto" | ||
| datetime=${props.buildInfo.builtAt} | ||
| title=${props.buildInfo.builtAt} | ||
| >${buildDate}</time |
There was a problem hiding this comment.
Add a copy path for the build timestamp
When Control UI is the surface support uses to identify a build, this renders the exact ISO timestamp only in datetime/title while the page wires a copy action only for the commit. Users can copy the full commit, but the visible/copyable Built field is just the localized date, so the exact build timestamp added for diagnostics is not practically copyable from the About page; add a timestamp or full build-info copy action here too.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a30b81730f
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| BUILD_GIT_COMMIT="$(openclaw_resolve_git_commit "$REPO_PATH")" | ||
| BUILD_TIMESTAMP="$(openclaw_resolve_build_timestamp)" | ||
| BUILD_ARGS+=(--build-arg "OPENCLAW_BUILD_TIMESTAMP=${BUILD_TIMESTAMP}") |
There was a problem hiding this comment.
Limit Podman build provenance to local image builds
When OPENCLAW_IMAGE/OPENCLAW_PODMAN_IMAGE points at a prebuilt image, this still resolves source build metadata before the script reaches the local-build vs pull branch. In environments that export a short or otherwise non-canonical GIT_COMMIT/GIT_SHA, or an invalid OPENCLAW_BUILD_TIMESTAMP, openclaw_resolve_* exits even though Podman setup only needs to pull/use the remote image; move this provenance block into the openclaw:local branch so remote-image installs do not depend on local source-build metadata.
Useful? React with 👍 / 👎.
|
Land-ready at What changed:
Proof:
Known proof gaps: none. |
|
Merged via squash.
|
* feat: show build identity in About screens * chore: leave root changelog to release automation * fix: translate Control UI About build details
Closes #103517
What Problem This Solves
OpenClaw's About surfaces showed only partial version information, which made it difficult to identify the exact source revision and build time of an installed app or Control UI artifact.
Why This Change Was Made
This adds one responsive Version / Commit / Built identity strip to the Control UI, Android, iOS, and macOS About surfaces. Build and release paths now pin one validated full Git SHA and UTC timestamp across the artifacts they produce; the UI keeps the compact SHA visible while exposing the full values for copying and diagnostics.
User Impact
Users and support engineers can identify an exact OpenClaw build from any supported About screen. The strip stays in one row when space permits, stacks cleanly on narrow or accessibility layouts, localizes the displayed UTC date, and preserves the full immutable values behind copy and accessibility actions.
Evidence
237/237focused routing and release-workflow tests passed on Testboxtbx_01kx5jv4anc0frr14ensghp2p6;git diff --checkclean.518tests with2platform-only skips.71targeted UI/Chromium tests, dedicated About E2E, and desktop/mobile visual verification passed (hosted run).