Skip to content

chore(release): cut mcp v0.8.0#5711

Merged
JSONbored merged 3 commits into
mainfrom
release-please--branches--main--components--mcp
Jul 14, 2026
Merged

chore(release): cut mcp v0.8.0#5711
JSONbored merged 3 commits into
mainfrom
release-please--branches--main--components--mcp

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.8.0 (2026-07-14)

Features

  • mcp: wire gittensory_feasibility_gate's claimStatus to the local claim ledger (#5157) (#5389) (91b235d)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @loopover/engine bumped from ^1.0.0 to ^2.0.0

This PR was generated with Release Please. See documentation.

@superagent-security

Copy link
Copy Markdown
Contributor

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

@JSONbored JSONbored self-assigned this Jul 14, 2026
JSONbored
JSONbored previously approved these changes Jul 14, 2026
@codecov

codecov Bot commented Jul 14, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.05%. Comparing base (6714f0c) to head (56ef84b).
⚠️ Report is 2 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #5711   +/-   ##
=======================================
  Coverage   95.05%   95.05%           
=======================================
  Files         581      581           
  Lines       46164    46164           
  Branches    14810    14810           
=======================================
  Hits        43880    43880           
  Misses       1523     1523           
  Partials      761      761           
Flag Coverage Δ
shard-1 43.97% <ø> (ø)
shard-2 35.70% <ø> (ø)
shard-3 32.28% <ø> (ø)
shard-4 33.02% <ø> (+<0.01%) ⬆️
shard-5 31.59% <ø> (ø)
shard-6 44.47% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

release-please's node-workspace plugin speculatively bumped this
package's @loopover/engine dependency to ^2.0.0, anticipating the
sibling engine-release branch (engine v2.0.0, a BREAKING change per
its own changelog: removes settings.gateCheckMode back-compat parsing
and renames several GITTENSORY_MINER_*/GITTENSORY_* env vars). Neither
this branch's own locally-committed packages/gittensory-engine (still
1.0.0 here) nor the npm registry has an engine@2.0.0 to resolve
against yet, so `npm ci`/`npm install` fail with ETARGET.

Reverting to ^1.0.0 (this package's mcp source doesn't reference
either breaking-change surface, but a major bump warrants a
deliberate, separately-verified upgrade rather than a speculative one
riding along on an unrelated version bump) unblocks this PR's own
genuine mcp 0.7.1->0.8.0 release independently. A future release-please
cycle, run after engine 2.0.0 is actually published, will propose the
real dependency bump.
@JSONbored
JSONbored merged commit 7a6ecba into main Jul 14, 2026
19 checks passed
@JSONbored
JSONbored deleted the release-please--branches--main--components--mcp branch July 14, 2026 07:07
@loopover-orb loopover-orb Bot added the gittensor:bug Gittensor-scored bug fix — scores a 0.05x multiplier. label Jul 14, 2026
@github-actions

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

autorelease: tagged gittensor:bug Gittensor-scored bug fix — scores a 0.05x multiplier.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant