@nanobpm/nano-workforce 0.148.0 → 0.148.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,3 +1,9 @@
1
+ ## [0.148.1](https://github.com/nanobpm/nano-workforce/compare/v0.148.0...v0.148.1) (2026-08-26)
2
+
3
+ ### Bug Fixes
4
+
5
+ * **prompts:** stop suggesting Depends-on: for parent-issue linking in feature.md ([#557](https://github.com/nanobpm/nano-workforce/issues/557)) ([3f698ba](https://github.com/nanobpm/nano-workforce/commit/3f698ba2c1ab4f43a154a8bf3f426aa343062ea4)), closes [Magikcraft/nano-bpm#988](https://github.com/Magikcraft/nano-bpm/issues/988) [#N](https://github.com/nanobpm/nano-workforce/issues/N) [#N](https://github.com/nanobpm/nano-workforce/issues/N) [#555](https://github.com/nanobpm/nano-workforce/issues/555)
6
+
1
7
  ## [0.148.0](https://github.com/nanobpm/nano-workforce/compare/v0.147.0...v0.148.0) (2026-08-26)
2
8
 
3
9
  ### Features
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@nanobpm/nano-workforce",
3
- "version": "0.148.0",
3
+ "version": "0.148.1",
4
4
  "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.",
5
5
  "type": "module",
6
6
  "main": "main.ts",
@@ -80,8 +80,15 @@ against the wrong base will not be merged into the epic.
80
80
  3. Implement `task.prompt`. Keep the change scoped to this slice only.
81
81
  4. Commit (sign off — this repo family enforces DCO: `git commit -s`), push the
82
82
  branch, and open a pull request with `gh pr create` describing the slice and
83
- linking the parent issue (`Depends-on:`/`Closes` as appropriate but read the
84
- scope-split rule below before you reach for `Closes`).
83
+ linking the parent issue with a **non-blocking** ref — `Refs #N` / `Part of #N`,
84
+ or `Closes #N` when you delivered its full scope (but read the scope-split rule
85
+ below before you reach for `Closes`). **Never link a parent issue with
86
+ `Depends-on:`** — that keyword is a merge barrier (scraped into the PR's
87
+ merge-dependency set and honored natively by Mergify), so pointing it at an
88
+ issue registers a bogus, unmergeable dependency. Reserve `Depends-on:` strictly
89
+ for real PR→PR merge barriers — i.e. only when this PR genuinely cannot merge
90
+ until another *PR* lands first, written as `Depends-on: owner/repo#123` (never
91
+ pointing at an issue).
85
92
  5. Clean up any scratch clone/worktree you created outside the commit.
86
93
 
87
94
  ## Closing keywords vs. scope splits — don't close a broader-scoped parent