@orderful/droid 0.55.1 → 0.55.2

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.
Files changed (8) hide show
  1. package/CHANGELOG.md +6 -0
  2. package/dist/tools/release/skills/release/SKILL.md +3 -3
  3. package/dist/tools/release/skills/release/references/templates.md +2 -2
  4. package/dist/tools/release/skills/release/references/workflows.md +7 -5
  5. package/package.json +1 -1
  6. package/src/tools/release/skills/release/SKILL.md +3 -3
  7. package/src/tools/release/skills/release/references/templates.md +2 -2
  8. package/src/tools/release/skills/release/references/workflows.md +7 -5
package/CHANGELOG.md CHANGED
@@ -1,5 +1,11 @@
1
1
  # @orderful/droid
2
2
 
3
+ ## 0.55.2
4
+
5
+ ### Patch Changes
6
+
7
+ - [#335](https://github.com/Orderful/droid/pull/335) [`92b08af`](https://github.com/Orderful/droid/commit/92b08afeab65ad2e33c0e2b6735deff95927c2a1) Thanks [@frytyler](https://github.com/frytyler)! - release: only auto-lock branch on high-risk releases. Low-risk releases no longer attempt to lock the branch by default. Use `--lock` flag or select High Risk to trigger auto-lock.
8
+
3
9
  ## 0.55.1
4
10
 
5
11
  ### Patch Changes
package/dist/tools/release/skills/release/SKILL.md CHANGED
@@ -27,7 +27,7 @@ Automate dev → master release ceremonies: create release PRs, lock branches du
27
27
 
28
28
  1. **`gh` CLI** — authenticated with access to target repos
29
29
  2. **Slack integration** — `droid integrations slack post` configured (optional, falls back to terminal)
30
- 3. **`branch-lock.yml`** — GitHub Action deployed to target repo (required for auto-lock on start + lock/unlock commands)
30
+ 3. **`branch-lock.yml`** — GitHub Action deployed to target repo (required for high-risk auto-lock + lock/unlock commands)
31
31
 
32
32
  ## Configuration
33
33
 
@@ -47,7 +47,7 @@ If no repos have `release_branch` set, tell user:
47
47
 
48
48
  ## Custom Instructions
49
49
 
50
- Any command accepts a ` -- {instruction}` suffix. Split on the **first** ` -- ` (space-dash-dash-space): left is the command and its args, right is additional context or instruction to carry through the entire execution. Note: flag-style `--no-lock` uses `--flag` syntax (no surrounding spaces) and is distinct from this separator.
50
+ Any command accepts a ` -- {instruction}` suffix. Split on the **first** ` -- ` (space-dash-dash-space): left is the command and its args, right is additional context or instruction to carry through the entire execution. Note: flag-style `--lock` uses `--flag` syntax (no surrounding spaces) and is distinct from this separator.
51
51
 
52
52
  Example: `/release start -- notify #releases-eng channel instead of the default`
53
53
 
@@ -55,7 +55,7 @@ Example: `/release start -- notify #releases-eng channel instead of the default`
55
55
 
56
56
  | Command | Action |
57
57
  |---------|--------|
58
- | `/release start [repo] [--no-lock]` | Create release PR + auto-lock branch + notify Slack |
58
+ | `/release start [repo] [--lock]` | Create release PR + notify Slack (auto-locks on high-risk or `--lock`) |
59
59
  | `/release merge [repo]` | Merge release PR (only if checks pass) + notify Slack |
60
60
  | `/release lock [repo]` | Lock release branch (confirms first) |
61
61
  | `/release unlock [repo]` | Unlock release branch |
package/dist/tools/release/skills/release/references/templates.md CHANGED
@@ -21,7 +21,7 @@ All Slack messages are posted via `droid integrations slack post`. Format as Sla
21
21
  Posted with :droid:
22
22
  ```
23
23
 
24
- If `--no-lock` was used, omit the lock line.
24
+ Only include the lock line if the branch was actually locked (high-risk release, high-risk PRs detected, or `--lock` flag). Omit it for low-risk releases without locking.
25
25
 
26
26
  If `HIGH_RISK_PRS` is non-empty, append the following block after `{pr_summary}` (before `Posted with :droid:`):
27
27
  ```
@@ -135,7 +135,7 @@ Release open for review — {repo_name}
135
135
  Lock: {release_branch} locked (no merges until release completes)
136
136
  ```
137
137
 
138
- If `--no-lock` was used, omit the Lock line.
138
+ Only include the Lock line if the branch was actually locked. Omit it for low-risk releases without locking.
139
139
 
140
140
  If `HIGH_RISK_PRS` is non-empty, append:
141
141
  ```
package/dist/tools/release/skills/release/references/workflows.md CHANGED
@@ -25,11 +25,11 @@ git -C {repo_path} remote get-url origin
25
25
 
26
26
  ---
27
27
 
28
- ## `/release start [repo] [--no-lock]`
28
+ ## `/release start [repo] [--lock]`
29
29
 
30
- Create a release PR, auto-lock the release branch, and notify Slack.
30
+ Create a release PR and notify Slack.
31
31
 
32
- **Auto-lock is on by default.** The branch is locked immediately after the PR is created to prevent blind merges during CI. Pass `--no-lock` (or natural language like "start without locking") to skip.
32
+ **Auto-lock is off by default.** The branch is only locked automatically for **high-risk** releases (user selects "High Risk" at the risk prompt, or `HIGH_RISK_PRS` are detected). Pass `--lock` (or natural language like "start and lock") to force locking on any release.
33
33
 
34
34
  ### Steps
35
35
 
@@ -82,7 +82,7 @@ Create a release PR, auto-lock the release branch, and notify Slack.
82
82
 
83
83
  See `templates.md` for the PR body template.
84
84
 
85
- 6. **Auto-lock branch** (unless `--no-lock`):
85
+ 6. **Auto-lock branch** (only if risk is **High Risk**, `HIGH_RISK_PRS` is non-empty, or `--lock` was passed):
86
86
  ```bash
87
87
  gh workflow run branch-lock.yml \
88
88
  -f action=lock \
@@ -97,6 +97,8 @@ Create a release PR, auto-lock the release branch, and notify Slack.
97
97
  If `branch-lock.yml` is not found in the repo, warn but don't fail:
98
98
  "Could not auto-lock — `branch-lock.yml` not found in `{repo_name}`. Use `/release lock` manually after adding the workflow."
99
99
 
100
+ **Skip this step entirely for low-risk releases without `--lock`.**
101
+
100
102
  7. **Post to Slack:**
101
103
  ```bash
102
104
  node -e 'process.stdout.write(JSON.stringify({
@@ -150,7 +152,7 @@ Merge the release PR if all checks are green, then notify Slack.
150
152
 
151
153
  ## `/release lock [repo]`
152
154
 
153
- Manually lock the release branch. Use when you need to lock outside of `/release start` (which auto-locks).
155
+ Manually lock the release branch. Use when you need to lock a low-risk release, or lock outside of `/release start`.
154
156
 
155
157
  ### Steps
156
158
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@orderful/droid",
3
- "version": "0.55.1",
3
+ "version": "0.55.2",
4
4
  "description": "AI workflow toolkit for sharing skills, commands, and agents across the team",
5
5
  "type": "module",
6
6
  "bin": {
package/src/tools/release/skills/release/SKILL.md CHANGED
@@ -27,7 +27,7 @@ Automate dev → master release ceremonies: create release PRs, lock branches du
27
27
 
28
28
  1. **`gh` CLI** — authenticated with access to target repos
29
29
  2. **Slack integration** — `droid integrations slack post` configured (optional, falls back to terminal)
30
- 3. **`branch-lock.yml`** — GitHub Action deployed to target repo (required for auto-lock on start + lock/unlock commands)
30
+ 3. **`branch-lock.yml`** — GitHub Action deployed to target repo (required for high-risk auto-lock + lock/unlock commands)
31
31
 
32
32
  ## Configuration
33
33
 
@@ -47,7 +47,7 @@ If no repos have `release_branch` set, tell user:
47
47
 
48
48
  ## Custom Instructions
49
49
 
50
- Any command accepts a ` -- {instruction}` suffix. Split on the **first** ` -- ` (space-dash-dash-space): left is the command and its args, right is additional context or instruction to carry through the entire execution. Note: flag-style `--no-lock` uses `--flag` syntax (no surrounding spaces) and is distinct from this separator.
50
+ Any command accepts a ` -- {instruction}` suffix. Split on the **first** ` -- ` (space-dash-dash-space): left is the command and its args, right is additional context or instruction to carry through the entire execution. Note: flag-style `--lock` uses `--flag` syntax (no surrounding spaces) and is distinct from this separator.
51
51
 
52
52
  Example: `/release start -- notify #releases-eng channel instead of the default`
53
53
 
@@ -55,7 +55,7 @@ Example: `/release start -- notify #releases-eng channel instead of the default`
55
55
 
56
56
  | Command | Action |
57
57
  |---------|--------|
58
- | `/release start [repo] [--no-lock]` | Create release PR + auto-lock branch + notify Slack |
58
+ | `/release start [repo] [--lock]` | Create release PR + notify Slack (auto-locks on high-risk or `--lock`) |
59
59
  | `/release merge [repo]` | Merge release PR (only if checks pass) + notify Slack |
60
60
  | `/release lock [repo]` | Lock release branch (confirms first) |
61
61
  | `/release unlock [repo]` | Unlock release branch |
package/src/tools/release/skills/release/references/templates.md CHANGED
@@ -21,7 +21,7 @@ All Slack messages are posted via `droid integrations slack post`. Format as Sla
21
21
  Posted with :droid:
22
22
  ```
23
23
 
24
- If `--no-lock` was used, omit the lock line.
24
+ Only include the lock line if the branch was actually locked (high-risk release, high-risk PRs detected, or `--lock` flag). Omit it for low-risk releases without locking.
25
25
 
26
26
  If `HIGH_RISK_PRS` is non-empty, append the following block after `{pr_summary}` (before `Posted with :droid:`):
27
27
  ```
@@ -135,7 +135,7 @@ Release open for review — {repo_name}
135
135
  Lock: {release_branch} locked (no merges until release completes)
136
136
  ```
137
137
 
138
- If `--no-lock` was used, omit the Lock line.
138
+ Only include the Lock line if the branch was actually locked. Omit it for low-risk releases without locking.
139
139
 
140
140
  If `HIGH_RISK_PRS` is non-empty, append:
141
141
  ```
package/src/tools/release/skills/release/references/workflows.md CHANGED
@@ -25,11 +25,11 @@ git -C {repo_path} remote get-url origin
25
25
 
26
26
  ---
27
27
 
28
- ## `/release start [repo] [--no-lock]`
28
+ ## `/release start [repo] [--lock]`
29
29
 
30
- Create a release PR, auto-lock the release branch, and notify Slack.
30
+ Create a release PR and notify Slack.
31
31
 
32
- **Auto-lock is on by default.** The branch is locked immediately after the PR is created to prevent blind merges during CI. Pass `--no-lock` (or natural language like "start without locking") to skip.
32
+ **Auto-lock is off by default.** The branch is only locked automatically for **high-risk** releases (user selects "High Risk" at the risk prompt, or `HIGH_RISK_PRS` are detected). Pass `--lock` (or natural language like "start and lock") to force locking on any release.
33
33
 
34
34
  ### Steps
35
35
 
@@ -82,7 +82,7 @@ Create a release PR, auto-lock the release branch, and notify Slack.
82
82
 
83
83
  See `templates.md` for the PR body template.
84
84
 
85
- 6. **Auto-lock branch** (unless `--no-lock`):
85
+ 6. **Auto-lock branch** (only if risk is **High Risk**, `HIGH_RISK_PRS` is non-empty, or `--lock` was passed):
86
86
  ```bash
87
87
  gh workflow run branch-lock.yml \
88
88
  -f action=lock \
@@ -97,6 +97,8 @@ Create a release PR, auto-lock the release branch, and notify Slack.
97
97
  If `branch-lock.yml` is not found in the repo, warn but don't fail:
98
98
  "Could not auto-lock — `branch-lock.yml` not found in `{repo_name}`. Use `/release lock` manually after adding the workflow."
99
99
 
100
+ **Skip this step entirely for low-risk releases without `--lock`.**
101
+
100
102
  7. **Post to Slack:**
101
103
  ```bash
102
104
  node -e 'process.stdout.write(JSON.stringify({
@@ -150,7 +152,7 @@ Merge the release PR if all checks are green, then notify Slack.
150
152
 
151
153
  ## `/release lock [repo]`
152
154
 
153
- Manually lock the release branch. Use when you need to lock outside of `/release start` (which auto-locks).
155
+ Manually lock the release branch. Use when you need to lock a low-risk release, or lock outside of `/release start`.
154
156
 
155
157
  ### Steps
156
158