chore(release): cut ui-kit v0.2.0 - #5710
Merged
JSONbored merged 3 commits intoJul 14, 2026
Merged
Conversation
Contributor
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
JSONbored
previously approved these changes
Jul 14, 2026
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
loopover-ui | bb67215 | Commit Preview URL Branch Preview URL |
Jul 14 2026, 07:00 AM |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #5710 +/- ##
=======================================
Coverage 95.05% 95.05%
=======================================
Files 581 581
Lines 46164 46164
Branches 14810 14810
=======================================
Hits 43880 43880
Misses 1523 1523
Partials 761 761
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
Two independent bugs blocked this PR's own `npm ci`: 1. package-lock.json's own "packages/gittensory-ui-kit" entry was never updated past 0.1.0 (this branch only carries ui-kit's own version 0.1.0->0.2.0 bump in package.json/CHANGELOG, no lockfile sync commit landed) -- `npm ci` fails EUSAGE on the mismatch. 2. apps/gittensory-ui and apps/gittensory-miner-ui both declare "@loopover/ui-kit": "^0.1.0". Per semver, a caret range on a 0.x package means >=0.1.0 <0.2.0 -- it does NOT admit 0.2.0. Neither app is a release-please-managed package (release-please-config.json only lists the 4 packages/* components), so the node-workspace plugin never widens their ranges when ui-kit cuts a release. This is the same caret-ceiling bug class #4974 already fixed for engine's consumers, recurring here for ui-kit's. ui-kit 0.2.0 is a pure feature addition (no breaking changes per its own changelog), so widening both apps' range to >=0.1.0 <1.0.0 (safe for any future 0.x bump, not just this one) and regenerating the lockfile is a correct, low-risk fix -- unlike the engine-major-bump case, there's no breaking-change exposure to defer here.
loopover-orb
Bot
added
the
gittensor:bug
5 tasks
JSONbored
added a commit
that referenced
this pull request
Jul 14, 2026
Three independent, pre-existing gate breaks, none introduced by this branch -- found while chasing why release-please's PRs (#5710-5713) looked flaky under local parallel test runs, and confirmed to reproduce identically on a clean origin/main checkout: - test/unit/agent-sdk-driver.test.ts, ai-summaries.test.ts, upstream-ruleset.test.ts: each does real, non-trivial work (git subprocess round-trips, a 42-entry forbidden-word sweep, 29 sequential D1-backed scenarios) that reliably exceeds vitest's 15s default under load. Widened each to an explicit, realistic timeout instead of leaving them to flake. - test/unit/selfhost-grafana-dashboard.test.ts: 5f187c2 (#5716) fixed a real production bug -- Grafana's ${var:sqlstring} doesn't sql-quote a value that starts with $__, so the old $__all "All repos" sentinel leaked through unescaped and SQLite misparsed it as its own bind parameter, silently zeroing every "All"-filtered panel. That commit updated the dashboard JSON and two sibling test files but missed this one. - apps/gittensory-ui/public/openapi.json + 3 route/component .tsx files: 40e6cdf (#5715, the @gittensory -> @Loopover bot-mention rename) changed copy text but never regenerated the OpenAPI spec or ran prettier on the reflowed JSX text nodes, so ui:openapi:check and ui:lint both fail on main. Regenerated the spec (npm run ui:openapi) and ran eslint --fix on the affected files; both are mechanical, zero-semantic-diff outputs.
Contributor
Author
|
🤖 Created releases: 🌻 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 I have created a release beep boop
0.2.0 (2026-07-14)
Features
This PR was generated with Release Please. See documentation.