Skip to content

chore(release): cut engine v3.1.0 - #5807

Merged
JSONbored merged 3 commits into
mainfrom
release-please--branches--main--components--engine
Jul 14, 2026
Merged

chore(release): cut engine v3.1.0#5807
JSONbored merged 3 commits into
mainfrom
release-please--branches--main--components--engine

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

3.1.0 (2026-07-14)

Features

  • engine: add a load-testing harness for iterate-loop under concurrent load (#5781) (4b6b5c6), closes #5224
  • engine: extract content-lane's pure leaf modules to loopover-engine (#5775) (60ed3cd), closes #4880
  • engine: extract settings leaf modules to loopover-engine (#5779) (b570c11), closes #4879
  • engine: per-tenant configuration layer (#5804) (1fd8519), closes #4787
  • engine: per-tenant resource quota evaluation (#5801) (db74aa3), closes #4796
  • mcp: add the idea-intake bridge and loopover_intake_idea tool (#5792) (d60481e), closes #4798
  • mcp: deliver a completed loop iteration as a customer results payload (#5797) (9b3f4b2), closes #4801
  • mcp: evaluate when a rented loop should escalate to a human (#5806) (90f477e)
  • mcp: route ideas through intake into a loop claim plan (#5795) (48d2a39), closes #4799
  • mcp: stream loop progress to the customer via a progress snapshot (#5798) (96b8c42), closes #4800
  • miner: honor kill-switch mid-attempt during iterate-loop (#5799) (3525e95)

Fixes

  • engine: clamp rate-limit retryAfterMs to at most one window on a backward clock (#5855) (f35e354), closes #5829
  • rebrand: full-cutover rename miner/AMS per-repo and operator config filenames (#5765) (c93569d)
  • rebrand: full-cutover rename remaining internal gittensory runtime identifiers (#5761) (75450f1)
  • signals: require a code file before manifest_missing_tests fires (#5852) (ad011d3)

This PR was generated with Release Please. See documentation.

@superagent-security

Copy link
Copy Markdown
Contributor

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

@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--engine branch from de3d0a9 to 52a47ee Compare July 14, 2026 19:24
JSONbored
JSONbored previously approved these changes Jul 14, 2026
@JSONbored JSONbored self-assigned this Jul 14, 2026
@codecov

codecov Bot commented Jul 14, 2026

Copy link
Copy Markdown

❌ 3 Tests Failed:

Tests completed Failed Passed Skipped
16416 3 16413 12
View the top 3 failed test(s) by shortest run time
test/unit/check-engine-parity-script.test.ts > check-engine-parity script > engine version skew > uses default version readers against the real monorepo workspace
Stack Traces | 0.0701s run time
AssertionError: expected [ Array(1) ] to deeply equal []

- Expected
+ Received

- []
+ [
+   "packages/loopover-miner/expected-engine.version (3.0.0) is out of sync with packages/loopover-engine/package.json (3.1.0).",
+ ]

 ❯ test/unit/check-engine-parity-script.test.ts:498:31
test/unit/check-engine-parity-script.test.ts > check-engine-parity script > runEngineParityMain returns 0 for the real monorepo workspace
Stack Traces | 0.0795s run time
AssertionError: expected 1 to be +0 // Object.is equality

- Expected
+ Received

- 0
+ 1

 ❯ test/unit/check-engine-parity-script.test.ts:511:48
test/unit/check-engine-parity-script.test.ts > check-engine-parity script > prints a clean summary and exits 0 for the real repo state when run as a subprocess
Stack Traces | 1.17s run time
Error: Command failed: .../gittensory/node_modules/.bin/tsx scripts/check-engine-parity.ts
Engine-parity check found 1 issue(s):
packages/loopover-miner/expected-engine.version (3.0.0) is out of sync with packages/loopover-engine/package.json (3.1.0).

 ❯ test/unit/check-engine-parity-script.test.ts:516:20

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { status: 1, signal: null, output: [ null, '', 'Engine-parity check found 1 issue(s):\npackages/loopover-miner/expected-engine.version (3.0.0) is out of sync with packages/loopover-engine/package.json (3.1.0).\n' ], pid: 2756, stdout: '', stderr: 'Engine-parity check found 1 issue(s):\npackages/loopover-miner/expected-engine.version (3.0.0) is out of sync with packages/loopover-engine/package.json (3.1.0).\n' }

To view more test analytics, go to the Test Analytics Dashboard
📋 Got 3 mins? Take this short survey to help us improve Test Analytics.

JSONbored added a commit that referenced this pull request Jul 14, 2026
…5856)

scripts/check-engine-parity.ts requires packages/loopover-miner/expected-engine.version
to match packages/loopover-engine/package.json's version, but release-please's engine
component only ever touches files under packages/loopover-engine/**, so it can never
update that cross-package pin itself. This left every engine release PR structurally
unable to pass CI (confirmed on the engine-v3.1.0 release PR, #5807). Extends the
existing package-lock.json sync step to also write the pin whenever the engine branch's
version changes.
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--engine branch from 603ee0a to 1630241 Compare July 14, 2026 20:26
@JSONbored
JSONbored merged commit c7f5451 into main Jul 14, 2026
17 checks passed
@JSONbored
JSONbored deleted the release-please--branches--main--components--engine branch July 14, 2026 21:03
@github-actions

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

This was referenced Jul 14, 2026
This was referenced Jul 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment