chore(release): cut engine v3.0.0 - #5737
Merged
JSONbored merged 3 commits intoJul 14, 2026
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
loopover-ui | 3733515 | Commit Preview URL Branch Preview URL |
Jul 14 2026, 10:54 AM |
Contributor
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
JSONbored
previously approved these changes
Jul 14, 2026
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #5737 +/- ##
==========================================
+ Coverage 86.18% 95.07% +8.88%
==========================================
Files 581 581
Lines 46181 46181
Branches 14811 14811
==========================================
+ Hits 39802 43905 +4103
+ Misses 4967 1516 -3451
+ Partials 1412 760 -652
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
github-actions
Bot
force-pushed
the
release-please--branches--main--components--engine
branch
from
July 14, 2026 11:19
3733515 to
e5d387b
Compare
…3.0.0 cut - packages/loopover-miner/expected-engine.version: same recurring drift as the v2.0.0/v2.0.1 cuts, bumped to 3.0.0. - packages/loopover-miner/docs/env-reference.md: the Phase 5 directory-rename commit (#5743) missed regenerating this one doc's title. - test/unit/routes-focus-manifest.test.ts: hardcoded the pre-rename apps/gittensory-ui/ path in two wantedPaths assertions; the real .loopover.yml already correctly says apps/loopover-ui/. - packages/loopover-miner/package.json: tightened @loopover/engine from ^2.0.0 to ^3.0.0. On this branch specifically, engine's own package.json is already 3.0.0 but miner's declared range isn't (that update rides on miner's own release), so npm resolves a stale published 2.0.0 as a non-hoisted nested copy for miner -- which the doctor engine-version-skew check (and 3 real test files depending on it) correctly flags as broken. Same judgment call as #5729: miner's own source doesn't touch anything engine 3.0.0 removed (the Phase 4/5 breaking changes are CLI binary/tool names and directory paths, not engine's exported JS API), so tightening the range here is safe. Also updates the 2 tests that assert the literal fallback range string. - apps/loopover-ui/src/routeTree.gen.ts: TanStack Router's own regeneration, unrelated to the above -- included as-is since it's a generated file now back in sync with the real (still-unrenamed) route source file.
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
3.0.0 (2026-07-14)
⚠ BREAKING CHANGES
Features
This PR was generated with Release Please. See documentation.