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
You are performing a **Senior Release Engineer** audit on this diff. Your goal is to identify risks that could impact downstream users or system stability.
4
+
5
+
### 🚨 Critical Instructions
6
+
-**Ignore** linting, variable naming, or stylistic preferences.
7
+
-**Focus** on public API surface, data schemas, and logic flow.
8
+
-**Be Concise**: Use bullet points. If no risks are found, state "No breaking changes identified."
9
+
10
+
---
11
+
12
+
### 1. 🛠️ Public API & Contract Changes
13
+
Identify any modifications to the public-facing interface.
14
+
-**Removals/Renames**: Are any classes, methods, or variables renamed or removed?
15
+
-**Signature Changes**: Have parameter types or return types changed in a way that breaks existing calls?
16
+
-**Defaults**: Have default values for arguments changed?
17
+
18
+
### 2. 🏗️ Architectural Integrity
19
+
-**Dependency Changes**: Highlight any new external libraries or significant version bumps.
20
+
-**Side Effects**: Are there new global states, singletons, or changes to how the application initializes?
21
+
-**Resource Usage**: Does this diff introduce patterns that might impact memory or CPU (e.g., new loops, heavy recursive calls)?
22
+
23
+
### 3. 📉 Backward Compatibility & Data
24
+
-**Persistence**: If applicable, do database schema changes or file format changes require a migration?
25
+
-**Protocol**: If this communicates via API/WebSockets, is the payload structure still compatible with the previous version?
26
+
27
+
### 4. 🧪 Testing & Validation
28
+
-**Coverage Gap**: Are there major logic additions that lack corresponding test files in the diff?
29
+
-**Edge Cases**: Identify at least one "what-if" scenario that might cause a failure (e.g., "What if the network is down during this new initialization step?").
30
+
31
+
---
32
+
33
+
### 🏁 Summary Verdict
34
+
Provide a 1-sentence summary of the "Safety" of this release candidate.
console.error(`Error checking for existing comments: ${error.message}`);
51
+
returntrue;// Fail closed to avoid duplicates if we can't verify
52
+
}
53
+
}
54
+
55
+
56
+
functionbuildBody({ prompt, headRef }){
57
+
return[
58
+
"@coderabbit review",
59
+
"",
60
+
MARKER,
61
+
"",
62
+
"## 🚀 Release Gate: Cumulative Audit",
63
+
"> **Notice to Reviewer**: This is a checkpoint PR for a new release. While the diff here primarily updates versioning and the Changelog, your audit must cover the **entire cumulative scope** of changes since the last version tag.",
64
+
"",
65
+
"### 🎯 Audit Objectives",
66
+
"- Analyze all features merged into `main` since the previous release.",
67
+
"- Identify breaking changes in the public API or protocol.",
68
+
"- Verify architectural integrity across the Hiero SDK Python modules.",
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,6 +27,7 @@ This changelog is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.
27
27
- Refactored the Advanced Issue Template to ensure PR-level quality checklists do not block maintainers during issue creation (#2036)
28
28
- Add automated label sync workflow to propagate labels from linked issues to pull requests (#1716)
29
29
- chore: update spam list (#2035)
30
+
- Add CodeRabbit release gate workflow and prompt for PR audits `release-pr-prompt.md`, `release-pr-coderabbit-gate.yml` and `release-pr-coderabbit-gate.js`
0 commit comments