chore(release): cut miner v3.0.0 - #5736
Closed
github-actions[bot] wants to merge 2 commits into
Closed
Conversation
JSONbored
previously approved these changes
Jul 14, 2026
|
github-actions
Bot
force-pushed
the
release-please--branches--main--components--miner
branch
from
July 14, 2026 10:36
68eb80b to
6aaea55
Compare
![superagent-security[bot]](https://avatars.githubusercontent.com/in/3287076?s=60&v=4){kind=small}
superagent-security
Bot
added
the
pr:flagged
github-actions
Bot
changed the title
github-actions
Bot
force-pushed
the
release-please--branches--main--components--miner
branch
from
July 14, 2026 11:19
0ec8db9 to
4d63070
Compare
Contributor
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
superagent-security
Bot
removed
the
pr:flagged
github-actions
Bot
force-pushed
the
release-please--branches--main--components--miner
branch
3 times, most recently
from
July 14, 2026 21:05
ed70531 to
2932d6f
Compare
17 tasks
JSONbored
force-pushed
the
release-please--branches--main--components--miner
branch
from
July 14, 2026 21:44
c118303 to
049dcf0
Compare
JSONbored
added a commit
that referenced
this pull request
Jul 14, 2026
test/unit/miner-cli.test.ts asserted the CLI's --version output and packages/loopover-miner/package.json's version equal a literal "2.0.0", so the test broke on every miner version bump (confirmed live on the miner-v3.0.0 release PR, #5736). packages/loopover-mcp's equivalent test (mcp-cli-basics.test.ts) already reads its package.json version dynamically -- match that pattern here so this compares the CLI's resolved version against the real current package.json version instead of a frozen literal, which is what both tests' own names already claimed to check.
JSONbored
added a commit
that referenced
this pull request
Jul 14, 2026
#5891) test/unit/miner-cli.test.ts asserted the CLI's --version output and packages/loopover-miner/package.json's version equal a literal "2.0.0", so the test broke on every miner version bump (confirmed live on the miner-v3.0.0 release PR, #5736). packages/loopover-mcp's equivalent test (mcp-cli-basics.test.ts) already reads its package.json version dynamically -- match that pattern here so this compares the CLI's resolved version against the real current package.json version instead of a frozen literal, which is what both tests' own names already claimed to check.
github-actions
Bot
force-pushed
the
release-please--branches--main--components--miner
branch
from
July 14, 2026 22:02
049dcf0 to
9f4116a
Compare
18 tasks
github-actions
Bot
force-pushed
the
release-please--branches--main--components--miner
branch
from
July 14, 2026 22:49
73f19b3 to
6c464c1
Compare
Owner
|
Closing to let release-please regenerate this branch from current main — stale, no new miner-specific commits to trigger a self-heal since main advanced (engine v3.1.1 + PAT auth fix + cross-repo-eval fix all merged). Will be recreated fresh on the next run. |
loopover-orb
Bot
added
the
gittensor:bug
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
3.0.0 (2026-07-14)
⚠ BREAKING CHANGES
Features
Fixes
This PR was generated with Release Please. See documentation.