@wipcomputer/wip-ai-devops-toolbox 1.9.71-alpha.8 → 1.9.71-alpha.9
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 +53 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,58 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 1.9.71-alpha.9 (2026-04-05)
|
|
4
|
+
|
|
5
|
+
# v1.9.71-alpha.8
|
|
6
|
+
|
|
7
|
+
## wip-release: automatic PR flow for protected main (Phase 4)
|
|
8
|
+
|
|
9
|
+
When `git push origin main` fails with GitHub's "protected branch" rejection (`GH006: Changes must be made through a pull request`), wip-release now automatically:
|
|
10
|
+
|
|
11
|
+
1. Creates a release branch `cc-mini/release-v<version>` at the current commit
|
|
12
|
+
2. Pushes the branch to origin
|
|
13
|
+
3. Opens a PR via `gh pr create` with title `release: v<version>`
|
|
14
|
+
4. Merges the PR via `gh pr merge --merge --delete-branch`
|
|
15
|
+
5. Pushes the tag separately (tags bypass branch protection on most GitHub setups)
|
|
16
|
+
6. Fast-forwards local main so downstream steps (deploy-public, etc.) have a clean state
|
|
17
|
+
|
|
18
|
+
Previously this was a 4-command manual workflow every release:
|
|
19
|
+
|
|
20
|
+
```
|
|
21
|
+
git branch cc-mini/release-alpha-N
|
|
22
|
+
git push -u origin cc-mini/release-alpha-N
|
|
23
|
+
gh pr create --base main --head cc-mini/release-alpha-N --title '...'
|
|
24
|
+
gh pr merge <pr> --merge --delete-branch
|
|
25
|
+
git push origin v<version>
|
|
26
|
+
```
|
|
27
|
+
|
|
28
|
+
Every release. Every time. Eliminated.
|
|
29
|
+
|
|
30
|
+
## Fallback behavior
|
|
31
|
+
|
|
32
|
+
If any step of the auto-PR flow fails (gh CLI missing, PR create failure, merge failure, tag push failure), wip-release logs a concrete recovery command for the exact failure mode and continues (non-fatal, matches prior push-failed behavior). The user can always complete the remaining steps manually.
|
|
33
|
+
|
|
34
|
+
## Direct push still works
|
|
35
|
+
|
|
36
|
+
If the repo allows direct push to main (typical for private staging repos), wip-release tries direct push first and only falls back to the PR flow on the specific GH006 / "protected branch" error. No behavioral change for unprotected repos.
|
|
37
|
+
|
|
38
|
+
## Files changed
|
|
39
|
+
|
|
40
|
+
- `tools/wip-release/core.mjs`: new `pushReleaseWithAutoPr(repoPath, newVersion, level)` and `logPushFailure(result, tag)` helpers. Three push sites in `release()`, `releaseHotfix()`, `releasePrerelease()` migrated to use the helper.
|
|
41
|
+
- `tools/wip-release/package.json`: 1.9.72 -> 1.9.73
|
|
42
|
+
- `CHANGELOG.md`: entry added
|
|
43
|
+
|
|
44
|
+
## Verified
|
|
45
|
+
|
|
46
|
+
- Module imports cleanly via `node -e "import('./tools/wip-release/core.mjs')"`.
|
|
47
|
+
- Error detection regex handles GH006 variants: `/protected branch|GH006|Changes must be made through a pull request/i`.
|
|
48
|
+
- All three release tracks (stable, prerelease, hotfix) use the same helper.
|
|
49
|
+
|
|
50
|
+
## Cross-references
|
|
51
|
+
|
|
52
|
+
- `ai/product/bugs/release-pipeline/2026-04-05--cc-mini--release-pipeline-master-plan.md` Phase 4 (Incident 4)
|
|
53
|
+
- `ai/product/bugs/master-plans/bugs-plan-04-05-2026-002.md` Wave 2 phase 7
|
|
54
|
+
- Prior ship: alpha.7 closed Phases 1, 2, 8 of the same plan.
|
|
55
|
+
|
|
3
56
|
## 1.9.71-alpha.8 (2026-04-05)
|
|
4
57
|
|
|
5
58
|
# v1.9.71-alpha.8
|