chore(release): cut ui-kit v1.6.0

[JSONbored]

🤖 I have created a release beep boop

1.6.0 (2026-07-31)

Features

• analytics: complete the PostHog migration — retire Umami, fix the MCP event contract (#10177) (2cafde3), closes #8293 #8299 #10175 #10176
• ui-kit: relocate streaming-text, use-streaming-text, typing-indicator from miner-ui (#9239) (f4a0ee0)

Fixes

• observability: group AI generations by their real trace, and attribute spend per repo (#10187) (693aed8), closes #10185
• ui-kit: expose PaginationEllipsis More pages outside aria-hidden (#10136) (291fcd9), closes #10052
• ui-kit: render chart tooltip zero inside tabular-nums span (#10114) (21855f2), closes #10051
• ui-kit: stop useStreamingText cancel() from overwriting a settled status (#10121) (3d7fdbf)

Dependencies

• ui-kit: publish the stranded recharts v3 migration, and guard the class (#9977) (c6fcee9)

---

This PR was generated with Release Please. See documentation.

[superagent-security]

Superagent didn't find any vulnerabilities or security issues in this PR.

[loopover-orb]

Warning

⏸️ LoopOver review result - manual review recommended

_{Review updated: 2026-07-31 23:48:09 UTC}

4 files · 1 AI reviewer · 1 blocker · CI green · clean

⏸️ Suggested Action - Manual Review

Review summary
This is an automated release-please version bump for @​loopover/ui-kit from 1.5.1 to 1.6.0, mechanically updating package.json, .release-please-manifest.json, package-lock.json, and CHANGELOG.md. The version/manifest/lockfile numbers are all consistent with each other, and the CHANGELOG entries match the commits already merged to main per the file history shown. This is a standard bot-generated release PR with no hand-written logic to review.

Nits — 3 non-blocking

• The 'Build UI preview artifact' CI check failed with no detail provided; given this branch is 1 commit behind default, it's plausibly caused by something that landed on main after divergence rather than this PR's own diff — worth confirming before merge.
• The external brief's flagged 'no provenance attestation' and 'long package-lock.json' items are expected artifacts of any release-please bump and workspace monorepo, not defects introduced by this PR.
• Confirm the failing 'Build UI preview artifact' check by re-running against latest main before merging, per the standard release-please flow.

Concerns raised — review before merging

• No linked issue detected: No closing reference or linked issue number was found in the PR metadata/body. — If this PR is intended to solve an issue, link it explicitly in the PR body.

📋 Copy for AI agents — paste into your coding agent

Fix the following blocker(s) from this PR review:

1. No linked issue detected: No closing reference or linked issue number was found in the PR metadata/body. — If this PR is intended to solve an issue, link it explicitly in the PR body.

Decision drivers

• ❌ Code review — 1 blocker (1 reviewer)
• ❌ Gate result — Blocking (Repo-configured hard blocker found.)

Context & advisory signals — never blocks the verdict

Signal	Result	Evidence
Linked issue	✅ No-issue rationale	PR body explains why no issue is linked.
Related work	✅ No active overlap found	No same-issue or scoped active PR overlap found.
Change scope	✅ 20/20	Low review scope from cached public metadata (no linked issue context).
Validation posture	⚠️ 20/25	Preflight is ready, but the PR body does not name the validation run.
Contributor workload	✅ 10/10	Author activity: 9 registered-repo PR(s), 8 merged, 279 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 9 PR(s), 279 issue(s).
Improvement	ℹ️ Insufficient signal	risk: clean · value: insufficient-signal

Review context

• Author: JSONbored
• Role context: owner (maintainer lane)
• Public audience mode: oss maintainer
• Lane context: Repository registration is not available in the local LoopOver cache.
• Public profile languages: Python, TypeScript, Ruby, Go, MDX, Shell, Solidity, JavaScript
• Official Gittensor activity: 9 PR(s), 279 issue(s).
• PR-specific overlap: none found.

Contributor next steps

• Start here: Treat this as maintainer-lane context rather than normal contributor-lane activity.
• Then work through the remaining 2 steps in the Signals table above.

Signal definitions

• Related work = same linked issue, overlapping active PRs, or title/path similarity.
• Change scope = cached public metadata such as size labels, draft state, and review-burden hints.
• Validation posture = whether the PR provides enough public validation/test evidence for maintainer review.
• Contributor workload = public contributor activity and cleanup pressure, not a repo-wide quality failure.
• Contributor context = public GitHub/Gittensor identity context; non-Gittensor status is not a blocker.

🧪 Chat with LoopOver

Ask LoopOver a question about this PR directly in a comment — grounded only in the same cached, public-safe facts shown above, never a new claim.

• @loopover ask <question> answers contribution-quality Q&A with source citations and freshness.
• @loopover chat <question> answers in natural prose from cached decision-pack facts via local inference (maintainer/collaborator; read-only).
• A plain-language @loopover mention with a real question is routed to the closest matching read-only command automatically — no exact syntax required.

Full command reference: https://loopover.ai/docs/loopover-commands

🧪 Experimental — new and may change.

Decision record

• action: hold · clause: missing_linked_issue
• config: 5276e770ec25158090bd68bcd537e12912c1a06a0f5cbf7a08511c91bfb6ea39 · pack: oss-anti-slop · ci: passed
• record: 04eef384d8c69b02015268a80d453ffeafaccfe01e7868a0a188af5fe9a19a8d (schema v6, head 4dab961)

_{🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed}

---

💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →.

Checked by LoopOver, a quiet PR intelligence layer for OSS maintainers.

• Re-run LoopOver review

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	loopover-ui	4dab961	Commit Preview URL Branch Preview URL	Jul 31 2026, 11:06 PM

[codecov]

Bundle Report

Bundle size has no change ✅

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.28%. Comparing base (12f3c6a) to head (4dab961).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #10196      +/-   ##
==========================================
- Coverage   92.28%   92.28%   -0.01%     
==========================================
  Files         939      939              
  Lines      114775   114725      -50     
  Branches    27715    27710       -5     
==========================================
- Hits       105920   105870      -50     
  Misses       7553     7553              
  Partials     1302     1302              

Flag	Coverage Δ
backend	95.70% <ø> (ø)
engine	74.11% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 1 file with indirect coverage changes