@nanobpm/nano-workforce 0.178.1 → 0.178.2

package/.github/workflows/renovate.yml

@@ -3,17 +3,18 @@ name: Renovate
 # Self-hosted Renovate (issue #406). renovate.json declares the policy — auto-merge
 # non-major @nanobpm/* updates once CI is green, majors need a human — but nothing was
 # ever running it, so the config sat dormant and nwf stayed pinned to old @nanobpm/urban.
-# This workflow IS the runner: on a schedule (and on demand) it opens update PRs and, on a
-# later pass once the PR's CI is green, merges the automerge ones itself. We self-host via
-# GitHub Actions rather than the Mend hosted app so the whole capability is in-repo and
-# reproducible, with no external app-install state to drift.
+# This workflow IS the runner: on a schedule (and on demand) it opens update PRs and enables
+# GitHub-native auto-merge on the automerge ones, which ENQUEUES them into main's merge queue so
+# they land when the queue's speculative checks pass. We self-host via GitHub Actions rather than
+# the Mend hosted app so the whole capability is in-repo and reproducible, with no external
+# app-install state to drift.
 on:
   schedule:
-    # Every 3 hours. Renovate needs to run periodically not just to DISCOVER new versions,
-    # but to COME BACK and merge automerge PRs: renovate.json sets platformAutomerge:false
-    # (main is unprotected, so GitHub-native auto-merge is unavailable), which means Renovate
-    # performs the merge itself on a subsequent run once the PR's branch status is green.
-    # A few-hourly cadence keeps that merge latency low without burning Actions minutes.
+    # Every 3 hours. Renovate needs to run periodically to DISCOVER new versions and open/refresh
+    # update PRs. Once main went behind a merge queue, Renovate no longer self-merges; it enables
+    # GitHub-native auto-merge (platformAutomerge:true) which enqueues the PR, and the queue lands it
+    # when its checks pass. A few-hourly cadence keeps discovery latency low without burning Actions
+    # minutes.
     - cron: "0 */3 * * *"
   # On-demand runs for immediate pickup (e.g. right after a new urban publishes) and for
   # debugging with a raised log level.

package/CHANGELOG.md

@@ -1,3 +1,9 @@
+## [0.178.2](https://github.com/nanobpm/nano-workforce/compare/v0.178.1...v0.178.2) (2026-09-03)
+
+### Bug Fixes
+
+* **ci:** enqueue Renovate @nanobpm/* automerge via the merge queue ([#720](https://github.com/nanobpm/nano-workforce/issues/720)) ([a788c3c](https://github.com/nanobpm/nano-workforce/commit/a788c3cc664ee7324c0706bf5182d180b8a17c0e)), closes [#421](https://github.com/nanobpm/nano-workforce/issues/421)
+
 ## [0.178.1](https://github.com/nanobpm/nano-workforce/compare/v0.178.0...v0.178.1) (2026-09-03)
 
 ### Bug Fixes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nanobpm/nano-workforce",
-  "version": "0.178.1",
+  "version": "0.178.2",
   "description": "Nano Workforce — an Agent Graph Orchestration application for Agentic SDLC: durable BPMN processes that coordinate a graph of AI agents across the software delivery lifecycle.",
   "type": "module",
   "main": "main.ts",
@@ -64,7 +64,7 @@
     "lint:fix": "biome check --write app operations workers pages components scripts e2e main.ts"
   },
   "dependencies": {
-    "@nanobpm/agentic": "^0.11.0",
+    "@nanobpm/agentic": "^0.12.0",
     "@nanobpm/urban": "^0.90.0",
     "bpmn-auto-layout": "^2.0.0-alpha.2"
   },

package/renovate.json

@@ -3,11 +3,11 @@
   "extends": ["config:recommended"],
   "packageRules": [
     {
-      "description": "Auto-merge non-major @nanobpm/* updates once CI is green. These are first-party packages we publish from nano-ide; CI (typecheck + test) is the gate. For 0.x pins a caret range locks the minor, so Renovate's range bump is what actually pulls a new minor through; automerging it keeps nwf on the latest urban without manual PRs. platformAutomerge is off because main is unprotected, so Renovate waits for its own green branch status before merging.",
+      "description": "Auto-merge non-major @nanobpm/* updates once CI is green. These are first-party packages we publish from nano-ide; CI (typecheck + test) is the gate. For 0.x pins a caret range locks the minor, so Renovate's range bump is what actually pulls a new minor through; automerging it keeps nwf on the latest agentic/urban without manual PRs. platformAutomerge is ON because main is now protected by an active ruleset with a GitHub merge queue (merge_queue rule): a direct self-merge is rejected by the queue, so Renovate must enable GitHub-native auto-merge, which ENQUEUES the PR and lets it land when the queue's speculative checks pass. (Historically this was false when main was unprotected; leaving it false silently wedged green update PRs open — e.g. the agentic 0.11->0.12 bump sat unmerged for weeks.)",
       "matchPackageNames": ["/^@nanobpm//"],
       "matchUpdateTypes": ["minor", "patch"],
       "automerge": true,
-      "platformAutomerge": false
+      "platformAutomerge": true
     },
     {
       "description": "Major @nanobpm/* updates may be breaking - require a human to review and merge.",