@programinglive/dev-workflow-mcp-server 1.3.9 → 1.3.10
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 +7 -0
- package/docs/WORKFLOW-BEST-PRACTICES.md +44 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,13 @@
|
|
|
2
2
|
|
|
3
3
|
All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.
|
|
4
4
|
|
|
5
|
+
### [1.3.10](https://github.com/programinglive/dev-workflow-mcp-server/compare/v1.3.9...v1.3.10) (2025-11-22)
|
|
6
|
+
|
|
7
|
+
|
|
8
|
+
### 📝 Documentation
|
|
9
|
+
|
|
10
|
+
* add workflow best practices to eliminate forced releases ([6bcac42](https://github.com/programinglive/dev-workflow-mcp-server/commit/6bcac42bc9f30cbfa0a27e36a90af303d244d863))
|
|
11
|
+
|
|
5
12
|
### [1.3.9](https://github.com/programinglive/dev-workflow-mcp-server/compare/v1.3.8...v1.3.9) (2025-11-22)
|
|
6
13
|
|
|
7
14
|
|
|
@@ -0,0 +1,44 @@
|
|
|
1
|
+
# Workflow Best Practices
|
|
2
|
+
|
|
3
|
+
## Correct Release Workflow Order
|
|
4
|
+
|
|
5
|
+
To avoid needing `--force` flag for releases, follow this exact order:
|
|
6
|
+
|
|
7
|
+
1. **Start Task**: `mcp0_start_task`
|
|
8
|
+
2. **Fix/Implement**: Make your code changes
|
|
9
|
+
3. **Mark Fixed**: `mcp0_mark_bug_fixed`
|
|
10
|
+
4. **Tests**: `mcp0_create_tests` + `mcp0_run_tests` (or `mcp0_skip_tests` with reason)
|
|
11
|
+
5. **Documentation**: `mcp0_create_documentation`
|
|
12
|
+
6. **Ready Check**: `mcp0_check_ready_to_commit`
|
|
13
|
+
7. **Commit & Push**: `mcp0_commit_and_push`
|
|
14
|
+
8. **Release**: `mcp0_perform_release` ⚠️ **MUST come BEFORE complete_task**
|
|
15
|
+
9. **Complete**: `mcp0_complete_task`
|
|
16
|
+
|
|
17
|
+
## Common Mistakes
|
|
18
|
+
|
|
19
|
+
### ❌ Wrong Order (causes forced releases)
|
|
20
|
+
```
|
|
21
|
+
check_ready → commit → complete → release // WRONG!
|
|
22
|
+
```
|
|
23
|
+
|
|
24
|
+
### ✅ Correct Order
|
|
25
|
+
```
|
|
26
|
+
check_ready → commit → release → complete // CORRECT!
|
|
27
|
+
```
|
|
28
|
+
|
|
29
|
+
## Why This Matters
|
|
30
|
+
|
|
31
|
+
- `complete_task` **resets the workflow state**
|
|
32
|
+
- `perform_release` **checks the workflow state** before running
|
|
33
|
+
- If you complete before releasing, the state is cleared and release guards fail
|
|
34
|
+
- Using `--force` bypasses guards but doesn't fix the root cause
|
|
35
|
+
|
|
36
|
+
## State Transitions
|
|
37
|
+
|
|
38
|
+
1. After `commit_and_push`: `currentPhase = "release"`
|
|
39
|
+
2. After `perform_release`: `currentPhase = "ready_to_complete"`, `released = true`
|
|
40
|
+
3. After `complete_task`: State is reset to idle
|
|
41
|
+
|
|
42
|
+
## Solution
|
|
43
|
+
|
|
44
|
+
Always call `perform_release` BEFORE `complete_task`. Never use `--force` unless absolutely necessary.
|
package/package.json
CHANGED