You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/bug_report.yml
+15Lines changed: 15 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -9,6 +9,8 @@ body:
9
9
value: |
10
10
Thanks for filing this report. Keep every answer concise, reproducible, and grounded in observed evidence.
11
11
Do not speculate or infer beyond the evidence. If a narrative section cannot be answered from the available evidence, respond with exactly `NOT_ENOUGH_INFO`.
12
+
13
+
If this is a plugin beta-release blocker, rename the issue title to `Beta blocker: <plugin-name> - <summary>` and apply the `beta-blocker` label after filing.
12
14
- type: dropdown
13
15
id: bug_type
14
16
attributes:
@@ -20,6 +22,19 @@ body:
20
22
- Behavior bug (incorrect output/state without crash)
21
23
validations:
22
24
required: true
25
+
- type: dropdown
26
+
id: beta_blocker
27
+
attributes:
28
+
label: Beta release blocker
29
+
description: >
30
+
Choose `Yes` only if this blocks plugin compatibility during the current beta release window.
31
+
Selecting `Yes` does not apply the label automatically. You must also rename the issue title
32
+
to `Beta blocker: <plugin-name> - <summary>` for the automation to apply the `beta-blocker` label.
Copy file name to clipboardExpand all lines: .github/pull_request_template.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,8 @@
2
2
3
3
Describe the problem and fix in 2–5 bullets:
4
4
5
+
If this PR fixes a plugin beta-release blocker, title it `fix(<plugin-id>): beta blocker - <summary>` and link the matching `Beta blocker: <plugin-name> - <summary>` issue labeled `beta-blocker`. Contributors cannot label PRs, so the title is the PR-side signal for maintainers and automation.
Copy file name to clipboardExpand all lines: docs/plugins/building-plugins.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -229,8 +229,9 @@ internal imports — never import your own plugin through its SDK path.
229
229
1. Watch for GitHub release tags on [openclaw/openclaw](https://github.com/openclaw/openclaw/releases) and subscribe via `Watch` > `Releases`. Beta tags look like `v2026.3.N-beta.1`. You can also turn on notifications for the official OpenClaw X account [@openclaw](https://x.com/openclaw) for release announcements.
230
230
2. Test your plugin against the beta tag as soon as it appears. The window before stable is typically only a few hours.
231
231
3. Post in your plugin's thread in the `plugin-forum` Discord channel after testing with either `all good` or what broke. If you do not have a thread yet, create one.
232
-
4. If something breaks, ship a fix PR to `main` and drop the link in your thread. Blockers with a PR get merged; blockers without one might ship anyway. Maintainers watch these threads during beta testing.
233
-
5. Silence means green. If you miss the window, your fix likely lands in the next cycle.
232
+
4. If something breaks, open or update an issue titled `Beta blocker: <plugin-name> - <summary>` and apply the `beta-blocker` label. Put the issue link in your thread.
233
+
5. Open a PR to `main` titled `fix(<plugin-id>): beta blocker - <summary>` and link the issue in both the PR and your Discord thread. Contributors cannot label PRs, so the title is the PR-side signal for maintainers and automation. Blockers with a PR get merged; blockers without one might ship anyway. Maintainers watch these threads during beta testing.
234
+
6. Silence means green. If you miss the window, your fix likely lands in the next cycle.
0 commit comments