Skip to content

chore(footer): the viewer link goes to xbrlkit.com - #64

Merged
jfrench9 merged 1 commit into
mainfrom
chore/viewer-footer
Sep 9, 2026
Merged

jfrench9 merged 1 commit into
mainfrom
chore/viewer-footer

Conversation

@jfrench9

@jfrench9 jfrench9 commented Sep 9, 2026

Copy link
Copy Markdown
Member

Summary

The holon viewer became the xbrlkit viewer on 2026-09-09 and moved to https://xbrlkit.com. The landing footer that every RoboSystems app renders links it, so the link text and destination follow. The old host, holon.robosystems.ai, keeps serving the same app as an alias, so apps on the current core release are not broken in the meantime; this just stops pointing new visitors at the old name.

Changes

  • ui-components/layout/LandingFooter.tsx — the footer entry reads "xbrlkit viewer" and links https://xbrlkit.com; the comment names it. Same external-link treatment (absolute URL, new tab) as before.

Consumer Impact

A visible string and an href in the shared footer; no exports, props, or types change. Picks up in robosystems-app, roboledger-app, and roboinvestor-app on their next bump to the core release that carries this.

Testing

npm run format:check, npm run lint (12 pre-existing warnings, no errors), npm run typecheck clean. Not rendered in an app for this change.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Wrb85mvgMjYTHHSkKWFre4

The holon viewer became the xbrlkit viewer, at its own domain. The
landing footer every app renders links it by its name and new host. The
old host keeps serving as an alias, so nothing breaks in the interim.

Claude-Session: https://claude.ai/code/session_01Wrb85mvgMjYTHHSkKWFre4
@jfrench9
jfrench9 merged commit 5398f5b into main Sep 9, 2026
5 checks passed
@jfrench9
jfrench9 deleted the chore/viewer-footer branch September 9, 2026 17:19
jfrench9 added a commit that referenced this pull request Sep 9, 2026
`npm install` re-resolved the peer dependencies on every CI run, so an
upstream publish could turn main red between a PR's green run and its
merge. It did today: react-dom 19.3.0 was published two minutes before
react 19.3.0, and the merge of #64 landed in between. `npm ci` installs
exactly what the lockfile says, in both the test and publish workflows.

Claude-Session: https://claude.ai/code/session_01Wrb85mvgMjYTHHSkKWFre4
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.

1 participant