chore(release): cut ui-kit v1.0.0 - #5826
Closed
github-actions[bot] wants to merge 2 commits into
Closed
Conversation
Contributor
| \nSuperagent didn't find any vulnerabilities or security issues in this PR. |
JSONbored
previously approved these changes
Jul 14, 2026
|
github-actions
Bot
force-pushed
the
release-please--branches--main--components--ui-kit
branch
from
July 14, 2026 20:26
212b12f to
12c955e
Compare
JSONbored
force-pushed
the
release-please--branches--main--components--ui-kit
branch
from
July 14, 2026 22:00
ccbabaf to
99b306c
Compare
18 tasks
JSONbored
added a commit
that referenced
this pull request
Jul 14, 2026
…ap (#5904) apps/loopover-ui and apps/loopover-miner-ui both pinned "@loopover/ui-kit" to ">=0.1.0 <1.0.0", excluding the ui-kit-v1.0.0 release-please PR's target version and permanently blocking its npm ci (confirmed live on #5826). The 1.0.0 cut's only breaking-change entry is the gittensory->loopover rename, which both apps already completed, so there's no live incompatibility -- widen the ceiling to <2.0.0, preserving the existing below-next-major convention. Verified with npm run ui:typecheck and ui:lint (0 errors). Also reconciles package-lock.json's stale "@loopover/engine" requires entries for @loopover/mcp and @loopover/miner (still ^3.1.0 from an earlier release-please regeneration cycle) back to match their current package.json ranges (^1.0.0 / ^3.0.0) -- npm install surfaced this while regenerating the lockfile for the ui-kit range change above.
Owner
|
Closing to let release-please regenerate this branch from current main -- it went stale before the ui-kit consumer-range fix (#5904, widening apps/loopover-ui and apps/loopover-miner-ui's @loopover/ui-kit range past its 1.0.0 pre-release cap) merged, and ui-kit's own component had no new package-specific commits since to trigger a self-heal rebuild. CI is failing here with 'Missing: @loopover/ui-kit@0.2.0 from lock file' / range exclusion of the just-cut 1.0.0 version -- the exact issue #5904 already fixed on main. Will be recreated fresh (picking up the merged fix) on the next release-please run. |
loopover-orb
Bot
added
the
gittensor:bug
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
1.0.0 (2026-07-14)
⚠ BREAKING CHANGES
Features
This PR was generated with Release Please. See documentation.