chore(release): cut ui-kit v1.0.0 - #5751
Closed
github-actions[bot] wants to merge 3 commits into
Closed
Conversation
Contributor
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
JSONbored
previously approved these changes
Jul 14, 2026
|
…1.0.0 - apps/loopover-ui, apps/loopover-miner-ui: widened @loopover/ui-kit from ">=0.1.0 <1.0.0" to ">=0.1.0 <2.0.0". ui-kit's only breaking change is the Phase 5 directory rename (no API/export changes), so the same "accept any compatible minor within the verified major line" reasoning from the original >=0.1.0 <1.0.0 fix applies -- just extended past the 1.0.0 boundary now that it's real. Without this, the declared range no longer covered the local workspace version, so npm resolved a stale published 0.2.0 as a non-hoisted nested copy for both UI apps. That nested copy is a genuine node_modules package (not a workspace symlink), so Vite/vitest externalizes it and resolves its internal imports via native Node ESM -- which can't handle the package's own extensionless relative imports (moduleResolution: Bundler doesn't emit .js extensions, since it assumes a bundler; symlinked workspace packages get bundler-processed and tolerate this fine, real node_modules packages don't). Regenerating the lockfile after the range fix restores the workspace symlink and the whole ui:test suite (13 previously-failing component test files) passes again. - test/unit/routes-focus-manifest.test.ts: same stale apps/gittensory-ui/ path fix as the engine/mcp/miner branches. - packages/loopover-miner/docs/env-reference.md, worker-configuration.d.ts: generated artifacts the Phase 5 rename commit missed regenerating.
Owner
|
Closing to let release-please regenerate this branch from current main — it went stale (conflicting with unrelated main-side changes) because no new ui-kit commits landed since it was last built, so the idempotent regen had nothing to update. Will be recreated fresh 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.