chore(release): cut engine v0.2.0 - #4176
Merged
JSONbored merged 5 commits intoJul 8, 2026
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
gittensory-ui | c38e0bb | Commit Preview URL Branch Preview URL |
Jul 08 2026, 10:53 AM |
JSONbored
previously approved these changes
Jul 8, 2026
loopover-orb
Bot
added
gittensor:bug
6 tasks
github-project-automation
Bot
moved this to Todo
in Autonomous Miner System (Loopover AMS)
github-project-automation
Bot
moved this to Todo
in Self-Hosted Review Stack (LoopOver Orb)
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4176 +/- ##
=======================================
Coverage 93.74% 93.74%
=======================================
Files 387 387
Lines 36398 36398
Branches 13330 13330
=======================================
Hits 34120 34120
Misses 1621 1621
Partials 657 657
🚀 New features to boost your workflow:
|
npm ci failed with "Missing: @jsonbored/gittensory-engine@0.1.0 from lock file" once this PR bumped packages/gittensory-engine to 0.2.0: semver caret ranges for 0.x versions only allow patch bumps (^0.1.0 means >=0.1.0 <0.2.0), so gittensory-mcp's "^0.1.0" and gittensory-miner's exact "0.1.0" pin both broke on this release's own minor bump. Widened both to ">=0.1.0" -- these are internal, same-monorepo dependencies whose real compatibility guarantee comes from this repo's own test suite, not from strict semver-range enforcement against a pre-1.0 package expected to move through minor versions somewhat often.
Same root cause as the package-lock.json/dependency-range fixes already pushed to this branch: ENGINE_VERSION was a hardcoded literal that test/unit/engine-version.test.ts correctly caught as stale against this release's package.json bump. See fix/release-please-lockfile-sync (#4179) for the full story and verification.
JSONbored
force-pushed
the
release-please--branches--main--components--engine
branch
from
July 8, 2026 10:30
6aa2fe5 to
199d466
Compare
![superagent-security[bot]](https://avatars.githubusercontent.com/in/3287076?s=60&v=4){kind=small}
superagent-security
Bot
added
the
pr:flagged
…import Two fixes squashed onto this branch, both already landed on fix/release-please-lockfile-sync (#4179): - Superagent correctly flagged >=0.1.0 as overly permissive (unbounded above, would accept a future major/compromised version with no review). Capped at ">=0.1.0 <1.0.0" -- tolerates all current and future 0.x releases without needing a re-bump, while still rejecting 1.0.0+. - ENGINE_VERSION's readFileSync approach broke the Workers runtime test suite (no real filesystem in the workerd sandbox). Switched to a compile-time JSON import, matching src/services/mcp-compatibility.ts's existing pattern -- Node's ESM loader resolves it at runtime for real installs, while the Worker's own esbuild bundling inlines it at build time for the bundled path, so neither consumer ever does runtime file I/O.
packages/gittensory-mcp and packages/gittensory-miner both already pin @jsonbored/gittensory-engine to >=0.1.0 <1.0.0 (in package.json and package-lock.json). Superagent's check-run on this branch is stuck reporting the pre-fix finding; this empty commit forces a clean re-scan.
superagent-security
Bot
removed
the
pr:flagged
Contributor
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
github-project-automation
Bot
moved this from Todo
to Done
in Self-Hosted Review Stack (LoopOver Orb)
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-08)
Features
Fixes
This PR was generated with Release Please. See documentation.