You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Copy file name to clipboardExpand all lines: packages/gittensory-miner/CHANGELOG.md
-7Lines changed: 0 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -139,10 +139,3 @@
139
139
***miner:** wire recordOwnSubmission's write side into the real attempt pipeline ([#5678](https://github.com/JSONbored/gittensory/issues/5678)) ([ebb540d](https://github.com/JSONbored/gittensory/commit/ebb540d51c5ffa67581fb7e018e2ce9d439b8a30))
0 commit comments