chore(main): release engine-and-dependents libraries#7133
Conversation
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #7133 +/- ##
=======================================
Coverage 93.75% 93.75%
=======================================
Files 692 692
Lines 68851 68851
Branches 18781 18781
=======================================
Hits 64554 64554
Misses 3302 3302
Partials 995 995
Flags with carried forward coverage won't be shown. Click here to find out more. |
|
Caution 🛑 LoopOver review result - fixes requiredReview updated: 2026-07-17 23:45:25 UTC
Review summary Nits — 4 non-blocking
Why this is blocked
📋 Copy for AI agents — paste into your coding agentCI checks failing
Decision drivers
Context & advisory signals — never blocks the verdict
Review context
Contributor next steps
Signal definitions
🧪 Chat with LoopOverAsk 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.
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.
|
…ne-and-dependents
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
loopover-ui | 53f9950 | Commit Preview URL Branch Preview URL |
Jul 17 2026, 11:51 PM |
Bundle ReportBundle size has no change ✅ Affected Assets, Files, and Routes:view changes for bundle: loopover-uiAssets Changed:
|
Stale again since @loopover/mcp published 3.2.1 (this exact class of drift already hit and got fixed once this session, JSONbored#7115) -- blocked an unrelated auto-generated release PR's (JSONbored#7133) CI. The durable fix (auto-sync this after every mcp publish, instead of a human noticing red CI on an unrelated PR) is a separate follow-up.
Root cause traced as far as possible: release-please's own createReleases() (the step that actually tags a merged Release PR) sometimes finds nothing to tag, and createPullRequests() then aborts every subsequent run without ever completing the tag -- confirmed live across two separate linked-versions release cycles this session (JSONbored#7127, JSONbored#7133), both requiring a manual dispatch of each publish-*.yml workflow plus manually flipping the merged PR's autorelease:pending label. Matches multiple long-open, unresolved upstream issues (googleapis/release-please#1946/JSONbored#1444/JSONbored#1406), so it isn't something fixable from this repo's config alone. Adds a reconcile-stale-releases job that runs after every release-please attempt, independent of its outputs: compares each package's committed package.json version against what's actually live on npm, dispatches that package's publish workflow whenever they disagree (the same documented human-override path, automated), and flips any merged PR's autorelease label once every package is confirmed live -- unsticking release-please's own tracking for the next run. Also cleaned up one ancient, silently-stuck instance of the exact same bug (engine v1.0.0, autorelease:pending since long before this session).
🤖 I have created a release beep boop
engine: 3.2.2
3.2.2 (2026-07-17)
Fixes
mcp: 3.2.2
3.2.2 (2026-07-17)
Fixes
Dependencies
miner: 3.2.2
3.2.2 (2026-07-17)
Fixes
Dependencies
This PR was generated with Release Please. See documentation.