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

[JSONbored]

🤖 I have created a release beep boop

1.1.2 (2026-07-24)

Fixes

• ui-kit: don't hijack Cmd/Ctrl+B Bold in text fields (SidebarProvider) (#8305) (#8341) (2ae66d6)
• ui-kit: give PaginationLink's aria-disabled a real visual/interaction effect (#8359) (ee7eed6), closes #8307
• ui-kit: move focus ring to focus-visible on Select/Dialog/Sheet/NavigationMenu (#8335) (3f081c4), closes #8304
• ui-kit: respect prefers-reduced-motion across animated ui-kit and miner-ui components (#8360) (5558575), closes #8303

---

This PR was generated with Release Please. See documentation.

[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	fa81854	Commit Preview URL Branch Preview URL	Jul 24 2026, 03:44 PM

[superagent-security]

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

[codecov]

Bundle Report

Bundle size has no change ✅

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.50%. Comparing base (1dba0ec) to head (fc8d454).
⚠️ Report is 17 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #8342      +/-   ##
==========================================
+ Coverage   92.43%   92.50%   +0.07%     
==========================================
  Files         791      791              
  Lines       79320    79333      +13     
  Branches    23952    23960       +8     
==========================================
+ Hits        73317    73387      +70     
+ Misses       4866     4807      -59     
- Partials     1137     1139       +2     

Flag	Coverage Δ
shard-1	55.50% <ø> (-2.27%)	⬇️
shard-2	49.89% <ø> (+2.23%)	⬆️
shard-3	56.86% <ø> (+0.27%)	⬆️

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

[loopover-orb]

Warning

⏸️ LoopOver review result - manual review recommended

_{Review updated: 2026-07-24 15:00:40 UTC}

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

⏸️ Suggested Action - Manual Review

Review summary
Standard release-please automated version bump for @​loopover/ui-kit from 1.1.1 to 1.1.2, updating package.json, the manifest, the changelog, and the lockfile's version fields to match four already-merged fixes. All four hunks are consistent, mechanical, and match the changelog entries listed in the PR description.

Nits — 3 non-blocking

• The 'security' and 'Build UI preview artifact' CI checks failed with no detail provided; given this branch is 2 commits behind default, this is plausibly caused by changes that landed on default after divergence rather than a defect in this diff — worth rebasing to confirm before merging.
• Rebase onto the latest default branch to rule out the undetailed CI failures being caused by upstream drift rather than this release commit.
• Readiness score is below the configured threshold — Use the readiness panel as advisory maintainer context; the score does not block this PR.

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	⚠️ 1 scoped overlap	Top overlaps are listed below; lower-confidence bulk is hidden.
Change scope	❌ 8/20	High review scope from cached public metadata (no linked issue context).
Validation posture	⚠️ 12/25	Preflight needs author follow-up before maintainer review.
Contributor workload	✅ 10/10	Author activity: 14 registered-repo PR(s), 14 merged, 346 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 14 PR(s), 346 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 is configured for direct PR review.
• Public profile languages: not available
• Official Gittensor activity: 14 PR(s), 346 issue(s).
• Related work: Titles/paths share 8 meaningful terms. (PR #8273)

Contributor next steps

• Start here: Treat this as maintainer-lane context rather than normal contributor-lane activity.
• Then work through the remaining 5 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.

_{🟩 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