chore(release): cut miner v3.1.2 by JSONbored · Pull Request #7107 · JSONbored/loopover

JSONbored · 2026-07-17T21:34:45Z

🤖 I have created a release beep boop

3.1.2 (2026-07-17)

Fixes

miner: bound oauth-device-flow.js's GitHub fetches with a request timeout (cd9aedf)
miner: bound oauth-device-flow.js's GitHub fetches with a request timeout (77ca20f)
miner: fail closed when a chat-action handler throws (8ba48bd)
miner: fail closed when a chat-action handler throws (bdb11d9), closes #6989
release: scope MCP publish validation to its own package (86ee117)

Dependencies

The following workspace dependencies were updated
- dependencies
  - @loopover/engine bumped from ^3.0.0 to ^3.2.1

This PR was generated with Release Please. See documentation.

cloudflare-workers-and-pages · 2026-07-17T21:34:59Z

Deploying with Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
❌ Deployment failed View logs	loopover-ui	`53c23c7`	Jul 17 2026, 09:35 PM

superagent-security · 2026-07-17T21:35:08Z

Superagent didn't find any vulnerabilities or security issues in this PR.

codecov · 2026-07-17T21:46:22Z

⚠️ JUnit XML file not found

The CLI was unable to find any JUnit XML files to upload.
For more help, visit our troubleshooting guide.

loopover-orb · 2026-07-17T21:50:27Z

Caution

🛑 LoopOver review result - fixes required

_{Review updated: 2026-07-17 21:50:41 UTC}

4 files · 1 AI reviewer · 1 blocker · CI failing · blocked

🛑 Suggested Action - Manual Review

Review summary
This is an automated release-please version bump PR for @loopover/miner from 3.1.2, bundling package.json version bumps, manifest updates, CHANGELOG entries, and a lockfile diff — all mechanically generated and consistent with the referenced upstream fix commits. The diff is internally coherent: version strings, manifest, changelog, and lockfile all agree on 3.1.2 and the @loopover/engine ^3.2.1 bump.

Nits — 4 non-blocking

The listed CI failures (validate-tests, validate-code, Build UI preview artifact, etc.) are not attributable to anything in this diff, which touches only version metadata and lockfile — worth confirming these are pre-existing/unrelated failures before merging.
package-lock.json shows only a single-line diff excerpt, but per the external brief it's a ~20k-line file; standard for lockfile churn on a dependency bump, not a concern specific to this PR.
Verify the CI failures are unrelated to this release PR (e.g., pre-existing on the base branch) since a pure version-bump PR shouldn't affect validate-tests/validate-code/UI build outcomes.
Confirm the @loopover/engine 3.2.1 changes referenced by the bumped dependency don't introduce breaking changes consumed by the miner package beyond what's covered by the linked fix commits.

Why this is blocked

No linked issue detected — If this PR is intended to solve an issue, link it explicitly in the PR body.

📋 Copy for AI agents — paste into your coding agent

Fix the following blocker(s) from this PR review:

1. No linked issue detected — If this PR is intended to solve an issue, link it explicitly in the PR body.

CI checks failing

validate
validate-tests (5)
validate-tests (2)
validate-tests (6)
validate-tests (3)
validate-tests (1)
validate-tests (4)
validate-code
Workers Builds: loopover-ui — Workers Builds: loopover-ui
Build UI preview artifact

Decision drivers

❌ Code review — 1 blocker (1 reviewer)
❌ Gate result — Blocking (Repo-configured hard blocker found.)

Context & advisory signals — never blocks the verdict

Signal	Result	Evidence
Linked issue	✅ No-issue rationale	PR body explains why no issue is linked.
Related work	⚠️ 3 scoped overlaps	Top overlaps are listed below; lower-confidence bulk is hidden.
Change scope	❌ 8/20	High review scope from cached public metadata (no linked issue context).
Validation posture	✅ 25/25	PR body includes validation/test evidence.
Contributor workload	✅ 10/10	Author activity: 32 registered-repo PR(s), 25 merged, 368 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 32 PR(s), 368 issue(s).
Improvement	ℹ️ Insufficient signal	risk: clean · value: insufficient-signal · LLM: minor

Review context

Author: JSONbored
Role context: owner (maintainer lane)
Public audience mode: oss maintainer
Lane context: Repository is configured for direct PR review.
Public profile languages: Python, TypeScript, Ruby, Go, JavaScript, MDX, Shell, Solidity
Official Gittensor activity: 32 PR(s), 368 issue(s).
Related work: Titles/paths share 5 meaningful terms. (PR #7109)
Related work: Titles/paths share 7 meaningful terms. (PR #7108)
Related work: Titles/paths share 5 meaningful terms. (PR #7109, PR #7108)

Contributor next steps

Start here: Treat this as maintainer-lane context rather than normal contributor-lane activity.
Then work through the remaining 4 steps in the Signals table above.

Signal definitions

Related work = same linked issue, overlapping active PRs, or title/path similarity.
Change scope = cached public metadata such as size labels, draft state, and review-burden hints.
Validation posture = whether the PR provides enough public validation/test evidence for maintainer review.
Contributor workload = public contributor activity and cleanup pressure, not a repo-wide quality failure.
Contributor context = public GitHub/Gittensor identity context; non-Gittensor status is not a blocker.

🧪 Chat with LoopOver

Ask LoopOver a question about this PR directly in a comment — grounded only in the same cached, public-safe facts shown above, never a new claim.

@loopover ask <question> answers contribution-quality Q&A with source citations and freshness.
@loopover chat <question> answers in natural prose from cached decision-pack facts via local inference (maintainer/collaborator; read-only).
A plain-language @loopover mention with a real question is routed to the closest matching read-only command automatically — no exact syntax required.

Full command reference: https://loopover.ai/docs/loopover-commands

🧪 Experimental — new and may change.

_{🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed}

💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →.

Checked by LoopOver, a quiet PR intelligence layer for OSS maintainers.

Re-run LoopOver review

JSONbored · 2026-07-17T21:52:52Z

Superseded -- #7114 fixed release-please-config.json so engine's release and its dependents (mcp, miner) now land as one combined PR/commit, structurally eliminating the ordering race that made this PR's own branch stale. Closing to let release-please regenerate correctly under the new config.

The actual root cause of the mcp/miner v3.1.x release churn: engine's release and its dependents' (mcp, miner both carry a real runtime `dependencies` entry on it) release each landed as SEPARATE PRs/commits. release-please's node-workspace plugin still bumped a dependent's `@loopover/engine` version range the moment engine's version changed, but on the dependent's OWN branch -- so the dependent's package.json ended up requiring an engine version that existed nowhere (not locally, since engine's bump lived on a different unmerged branch; not on npm, since it hadn't published yet). `npm ci` failed with ETARGET until a human manually walked engine through to publish first, then updated the dependent's branch -- confirmed live across JSONbored#7086/JSONbored#7087/JSONbored#7107/JSONbored#7108. merge: true is the plugin's own purpose-built mechanism for exactly this: it combines a package with the dependents its OWN dependency-bump logic pulled in as candidates into ONE PR/commit, so engine's new version and its dependents' bumped ranges land together atomically. npm workspaces then resolves the dependency from the LOCAL checkout, which always satisfies the range regardless of npm registry publish timing or ordering -- eliminating the failure mode structurally rather than papering over it with an after-the-fact branch-update step. ui-kit has no dependency edge to any other package here, so it's never pulled into the merge and keeps its fully independent release cadence.

chore(release): cut miner v3.1.2

fce5aa6

JSONbored added the autorelease: pending label Jul 17, 2026

JSONbored force-pushed the release-please--branches--main--components--miner branch from 2a64265 to fce5aa6 Compare July 17, 2026 21:34

chore(release): sync package-lock.json

53c23c7

JSONbored self-assigned this Jul 17, 2026

loopover-orb Bot mentioned this pull request Jul 17, 2026

chore(release): cut mcp v3.1.2 #7108

Closed

JSONbored mentioned this pull request Jul 17, 2026

fix(release): merge engine's release with its dependents (mcp, miner) #7114

Merged

4 tasks

loopover-orb Bot added the gittensor:bug Gittensor-scored bug fix — scores a 0.05x multiplier. label Jul 17, 2026

loopover-orb Bot added the manual-review Gittensor contributor context label Jul 17, 2026

loopover-orb Bot mentioned this pull request Jul 17, 2026

chore(release): cut engine v3.2.1 #7109

Closed

JSONbored closed this Jul 17, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

chore(release): cut miner v3.1.2#7107

chore(release): cut miner v3.1.2#7107
JSONbored wants to merge 2 commits into
mainfrom
release-please--branches--main--components--miner

JSONbored commented Jul 17, 2026

Uh oh!

cloudflare-workers-and-pages Bot commented Jul 17, 2026 •

edited

Loading

Uh oh!

superagent-security Bot commented Jul 17, 2026

Uh oh!

codecov Bot commented Jul 17, 2026

Uh oh!

loopover-orb Bot commented Jul 17, 2026 •

edited

Loading

🛑 LoopOver review result - fixes required

Uh oh!

JSONbored commented Jul 17, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

JSONbored commented Jul 17, 2026

🤖 I have created a release beep boop

3.1.2 (2026-07-17)

Fixes

Dependencies

Uh oh!

cloudflare-workers-and-pages Bot commented Jul 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Deploying with Cloudflare Workers

Uh oh!

superagent-security Bot commented Jul 17, 2026

Uh oh!

codecov Bot commented Jul 17, 2026

⚠️ JUnit XML file not found

Uh oh!

loopover-orb Bot commented Jul 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🛑 LoopOver review result - fixes required

Uh oh!

JSONbored commented Jul 17, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

cloudflare-workers-and-pages Bot commented Jul 17, 2026 •

edited

Loading

loopover-orb Bot commented Jul 17, 2026 •

edited

Loading