@wipcomputer/wip-ai-devops-toolbox 1.9.52 → 1.9.53
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 +25 -0
- package/SKILL.md +1 -1
- package/_trash/RELEASE-NOTES-v1-9-53.md +22 -0
- package/package.json +1 -1
- package/tools/deploy-public/package.json +1 -1
- package/tools/post-merge-rename/package.json +1 -1
- package/tools/wip-branch-guard/guard.mjs +7 -6
- package/tools/wip-branch-guard/package.json +1 -1
- package/tools/wip-file-guard/package.json +1 -1
- package/tools/wip-license-guard/package.json +1 -1
- package/tools/wip-license-hook/package.json +1 -1
- package/tools/wip-readme-format/package.json +1 -1
- package/tools/wip-release/package.json +1 -1
- package/tools/wip-repo-init/package.json +1 -1
- package/tools/wip-repo-permissions-hook/package.json +1 -1
- package/tools/wip-repos/package.json +1 -1
- package/tools/wip-universal-installer/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -31,6 +31,31 @@
|
|
|
31
31
|
|
|
32
32
|
|
|
33
33
|
|
|
34
|
+
|
|
35
|
+
## 1.9.53 (2026-03-28)
|
|
36
|
+
|
|
37
|
+
# Release Notes: wip-ai-devops-toolbox v1.9.53
|
|
38
|
+
|
|
39
|
+
**One-line summary of what this release does**
|
|
40
|
+
|
|
41
|
+
Tell the story. What was broken or missing? What did we build? Why does the user care?
|
|
42
|
+
Write at least one real paragraph of prose. Not just bullets. The release notes gate
|
|
43
|
+
will block if there is no narrative. Bullets are fine for details, but the story comes first.
|
|
44
|
+
|
|
45
|
+
## The story
|
|
46
|
+
|
|
47
|
+
(Write a paragraph here. What was the problem? What does this release fix? Why does it matter?
|
|
48
|
+
This is what users read. Make it worth reading.)
|
|
49
|
+
|
|
50
|
+
## Issues closed
|
|
51
|
+
|
|
52
|
+
- #282
|
|
53
|
+
|
|
54
|
+
## How to verify
|
|
55
|
+
|
|
56
|
+
```bash
|
|
57
|
+
# Commands to test the changes
|
|
58
|
+
```
|
|
34
59
|
|
|
35
60
|
## 1.9.52 (2026-03-27)
|
|
36
61
|
|
package/SKILL.md
CHANGED
|
@@ -5,7 +5,7 @@ license: MIT
|
|
|
5
5
|
interface: [cli, module, mcp, skill, hook, plugin]
|
|
6
6
|
metadata:
|
|
7
7
|
display-name: "WIP AI DevOps Toolbox"
|
|
8
|
-
version: "1.9.
|
|
8
|
+
version: "1.9.53"
|
|
9
9
|
homepage: "https://github.com/wipcomputer/wip-ai-devops-toolbox"
|
|
10
10
|
author: "Parker Todd Brooks"
|
|
11
11
|
category: dev-tools
|
|
@@ -0,0 +1,22 @@
|
|
|
1
|
+
# Release Notes: wip-ai-devops-toolbox v1.9.53
|
|
2
|
+
|
|
3
|
+
**One-line summary of what this release does**
|
|
4
|
+
|
|
5
|
+
Tell the story. What was broken or missing? What did we build? Why does the user care?
|
|
6
|
+
Write at least one real paragraph of prose. Not just bullets. The release notes gate
|
|
7
|
+
will block if there is no narrative. Bullets are fine for details, but the story comes first.
|
|
8
|
+
|
|
9
|
+
## The story
|
|
10
|
+
|
|
11
|
+
(Write a paragraph here. What was the problem? What does this release fix? Why does it matter?
|
|
12
|
+
This is what users read. Make it worth reading.)
|
|
13
|
+
|
|
14
|
+
## Issues closed
|
|
15
|
+
|
|
16
|
+
- #282
|
|
17
|
+
|
|
18
|
+
## How to verify
|
|
19
|
+
|
|
20
|
+
```bash
|
|
21
|
+
# Commands to test the changes
|
|
22
|
+
```
|
package/package.json
CHANGED
|
@@ -89,13 +89,14 @@ const ALLOWED_BASH_PATTERNS = [
|
|
|
89
89
|
/\bldm\s+(install|init|doctor|stack|updates)\b/, // LDM OS commands modify ~/.ldm/, not the repo
|
|
90
90
|
/\brm\s+.*\.ldm\/state\//, // cleaning LDM state files only, not repo files
|
|
91
91
|
/\bclaude\s+mcp\b/, // MCP registration, not repo files
|
|
92
|
+
/\bmkdir\s+.*\.worktrees\b/, // creating .worktrees/ directory is part of the process
|
|
92
93
|
];
|
|
93
94
|
|
|
94
95
|
// Workflow steps for error messages (#213)
|
|
95
96
|
const WORKFLOW_ON_MAIN = `
|
|
96
97
|
The process: worktree -> branch -> commit -> push -> PR -> merge -> wip-release -> deploy-public.
|
|
97
98
|
|
|
98
|
-
Step 1: git worktree add
|
|
99
|
+
Step 1: git worktree add .worktrees/<repo>--<branch> -b cc-mini/your-feature
|
|
99
100
|
Step 2: Edit files in the worktree
|
|
100
101
|
Step 3: git add + git commit (with co-authors)
|
|
101
102
|
Step 4: git push -u origin cc-mini/your-feature
|
|
@@ -249,15 +250,15 @@ async function main() {
|
|
|
249
250
|
} catch {}
|
|
250
251
|
}
|
|
251
252
|
|
|
252
|
-
// Warn when creating worktrees outside
|
|
253
|
+
// Warn when creating worktrees outside .worktrees/ (#212)
|
|
253
254
|
const wtMatch = cmd.match(/\bgit\s+worktree\s+add\s+["']?([^\s"']+)/);
|
|
254
255
|
if (wtMatch) {
|
|
255
256
|
const wtPath = wtMatch[1];
|
|
256
|
-
if (!wtPath.includes('
|
|
257
|
-
deny(`WARNING: Creating worktree outside
|
|
257
|
+
if (!wtPath.includes('.worktrees')) {
|
|
258
|
+
deny(`WARNING: Creating worktree outside .worktrees/. Use: ldm worktree add <branch>
|
|
258
259
|
|
|
259
|
-
The convention is
|
|
260
|
-
Manual equivalent: git worktree add
|
|
260
|
+
The convention is .worktrees/<repo>--<branch>/ so worktrees are hidden and don't mix with real repos.
|
|
261
|
+
Manual equivalent: git worktree add .worktrees/<repo>--<branch> -b <branch>
|
|
261
262
|
|
|
262
263
|
This is a warning, not a block. If you need to create it here, retry.`);
|
|
263
264
|
process.exit(0);
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@wipcomputer/universal-installer",
|
|
3
|
-
"version": "1.9.
|
|
3
|
+
"version": "1.9.53",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"description": "The Universal Interface specification for agent-native software. Teaches your AI how to build repos with every interface: CLI, Module, MCP Server, OpenClaw Plugin, Skill, Claude Code Hook.",
|
|
6
6
|
"main": "detect.mjs",
|