chore(release): cut engine v2.0.0#5713
Merged
JSONbored merged 3 commits intoJul 14, 2026
Merged
Conversation
Contributor
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
JSONbored
previously approved these changes
Jul 14, 2026
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #5713 +/- ##
=======================================
Coverage 95.06% 95.06%
=======================================
Files 581 581
Lines 46179 46179
Branches 14811 14811
=======================================
Hits 43901 43901
Misses 1517 1517
Partials 761 761
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
github-actions
Bot
force-pushed
the
release-please--branches--main--components--engine
branch
from
July 14, 2026 06:39
4e5c39e to
6a46e5b
Compare
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| 🔵 In progress View logs |
loopover-ui | 6a46e5b | Jul 14 2026, 06:39 AM |
github-project-automation
Bot
moved this to Todo
in Autonomous Miner System (Loopover AMS)
loopover-orb
Bot
added
the
gittensor:bug
5 tasks
github-actions
Bot
force-pushed
the
release-please--branches--main--components--engine
branch
from
July 14, 2026 08:16
fb6fe18 to
926e620
Compare
….0 cut release-please regenerated this branch from current main, which reintroduced two issues already fixed once on the branch's prior incarnation: - package-lock.json was missing an entry for @loopover/engine@1.0.0 (a dependent's still-published-range requirement), so npm ci rejected it as out of sync. Regenerated via npm install. - packages/gittensory-miner/expected-engine.version still pinned 1.0.0, which scripts/check-engine-parity.ts's version-skew tripwire compares against the real packages/gittensory-engine/package.json (now 2.0.0) and fails on mismatch. Synced to 2.0.0, same as the prior cut.
JSONbored
added a commit
that referenced
this pull request
Jul 14, 2026
release-please regenerated this branch from current main, which reintroduced two issues already fixed once on the branch's prior incarnation: - packages/gittensory-miner/package.json's @loopover/engine dependency was speculatively cross-bumped to an exact "2.0.0" pin by release-please's node-workspace plugin, matching the engine component's own still-open, still-unpublished release PR (#5713). The local workspace member is still 1.0.0 on this branch (main hasn't merged that bump), and 2.0.0 isn't on the npm registry either, so npm ci failed with ETARGET. Reverted to "*" so the workspace-local link resolves regardless of which sibling version lands first, and dropped the now-inaccurate CHANGELOG "Dependencies" section. - test/unit/miner-cli.test.ts hardcoded "0.1.0" in the two assertions that check the real package/CLI version, stale against this cut's real 1.0.0.
github-project-automation
Bot
moved this from Todo
to Done
in Autonomous Miner System (Loopover AMS)
JSONbored
added a commit
that referenced
this pull request
Jul 14, 2026
* chore(release): cut miner v1.0.0 * chore(release): sync package-lock.json * fix: revert speculative engine pin and fix hardcoded version assertions release-please regenerated this branch from current main, which reintroduced two issues already fixed once on the branch's prior incarnation: - packages/gittensory-miner/package.json's @loopover/engine dependency was speculatively cross-bumped to an exact "2.0.0" pin by release-please's node-workspace plugin, matching the engine component's own still-open, still-unpublished release PR (#5713). The local workspace member is still 1.0.0 on this branch (main hasn't merged that bump), and 2.0.0 isn't on the npm registry either, so npm ci failed with ETARGET. Reverted to "*" so the workspace-local link resolves regardless of which sibling version lands first, and dropped the now-inaccurate CHANGELOG "Dependencies" section. - test/unit/miner-cli.test.ts hardcoded "0.1.0" in the two assertions that check the real package/CLI version, stale against this cut's real 1.0.0. --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: JSONbored <49853598+JSONbored@users.noreply.github.com>
Contributor
Author
|
🤖 Created releases: 🌻 |
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
2.0.0 (2026-07-14)
⚠ BREAKING CHANGES
Features
Fixes
This PR was generated with Release Please. See documentation.