@sweny-ai/core 0.1.10 → 0.1.11

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 (2) hide show
  1. package/dist/workflows/triage.js +8 -6
  2. package/package.json +1 -1
package/dist/workflows/triage.js CHANGED
@@ -104,9 +104,10 @@ Downstream nodes will act ONLY on novel findings. Duplicates will be +1'd automa
104
104
  4. Link to relevant commits, PRs, or existing issues.
105
105
 
106
106
  **For each DUPLICATE finding** (is_duplicate = true):
107
- 1. Find the existing issue using the issue tracker (check duplicate_of field).
108
- 2. Add a comment: "+1 — SWEny triage confirmed this issue is still active (seen again at {current UTC timestamp}). Latest context: {1-2 sentence summary}."
109
- 3. If the existing issue is closed/done, reopen it or note in the comment that the bug has recurred.
107
+ 1. Find the existing issue (check duplicate_of field).
108
+ 2. Check the issue's comments — if the most recent comment is already from SWEny (contains "+1") within the last 24 hours, skip adding another comment.
109
+ 3. Otherwise add a SHORT comment: "+1 — seen again {UTC timestamp}. {one sentence of new context}." (Keep it under 2 lines. No markdown headers, no emoji, no formatting.)
110
+ 4. If the existing issue is closed/done, reopen it.
110
111
 
111
112
  If context.issueTemplate is provided, use it as the format for new issue bodies. Otherwise use a clear structure with: Summary, Root Cause, Impact, Steps to Reproduce, and Recommended Fix.
112
113
 
@@ -118,9 +119,10 @@ Use whichever issue tracker is available to you. Output the created/updated issu
118
119
  instruction: `Every finding from the investigation was either a duplicate or low-priority. No new issues need to be created.
119
120
 
120
121
  For each **duplicate** finding (check the findings array for items where is_duplicate = true):
121
- 1. Find the existing issue using the issue tracker (check duplicate_of field).
122
- 2. Add a comment: "+1 — SWEny triage confirmed this issue is still active (seen again at {current UTC timestamp}). Latest context: {1-2 sentence summary of what was found this run}."
123
- 3. If the issue is closed/done, reopen it or note in the comment that the bug has recurred.
122
+ 1. Find the existing issue (check duplicate_of field).
123
+ 2. Check the issue's comments — if the most recent comment is already from SWEny (contains "+1") within the last 24 hours, skip adding another comment.
124
+ 3. Otherwise add a SHORT comment: "+1 — seen again {UTC timestamp}. {one sentence of new context}." (Keep it under 2 lines. No markdown headers, no emoji, no formatting.)
125
+ 4. If the issue is closed/done, reopen it.
124
126
 
125
127
  For **low priority** findings, log a brief note about why they were skipped.`,
126
128
  skills: ["linear", "github"],
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sweny-ai/core",
3
- "version": "0.1.10",
3
+ "version": "0.1.11",
4
4
  "type": "module",
5
5
  "bin": {
6
6
  "sweny": "./dist/cli/main.js"