Skip to content

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

Closed
JSONbored wants to merge 2 commits into
mainfrom
release-please--branches--main--components--mcp
Closed

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

Conversation

@JSONbored

Copy link
Copy Markdown
Owner

🤖 I have created a release beep boop

3.1.2 (2026-07-17)

Fixes

  • api: blunt slop-risk / issue-slop REST + CLI to match the MCP tools (#6990) (#7052) (9971476)
  • 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

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

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  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 5c78798 Jul 17 2026, 10:05 PM

@superagent-security

Copy link
Copy Markdown
Contributor

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

@JSONbored

Copy link
Copy Markdown
Owner Author

Superseded -- node-workspace's own merge:true (#7114) wasn't sufficient on its own; separate-pull-requests also needs to be false for release-please's cross-component Merge plugin to actually combine these. Closing to verify the follow-up fix.

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

codecov Bot commented Jul 17, 2026

Copy link
Copy Markdown

⚠️ JUnit XML file not found

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

@JSONbored
JSONbored deleted the release-please--branches--main--components--mcp branch July 17, 2026 22:45
galuis116 pushed a commit to galuis116/gittensory that referenced this pull request Jul 18, 2026
JSONbored#7114's node-workspace merge:true was insufficient -- verified against
release-please's own manifest.ts and docs/manifest-releaser.md that
separate-pull-requests: true is enforced as the final PR-splitting
decision regardless of what a plugin like node-workspace attempts
internally, so mcp/miner's Release PRs kept landing separately from
engine's even with that flag set (confirmed live: JSONbored#7119/JSONbored#7120/JSONbored#7121 still
required an unpublished @loopover/engine version each).

linked-versions is release-please's actual mechanism for overriding
per-component isolation for a named subset: {engine, mcp, miner} now
release as one PR/commit whenever any of them needs a release, since mcp
and miner both carry a real runtime dependency on engine. ui-kit has no
dependency edge to any of them and is not in the group, so it keeps its
fully independent cadence.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

autorelease: pending 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