opencode-sonarqube 1.2.32 → 1.2.34

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/index.js +57 -53
  2. package/package.json +1 -1
package/dist/index.js CHANGED
@@ -20876,49 +20876,46 @@ Git operation completed with changes. Consider running:
20876
20876
  if (result.block && args) {
20877
20877
  const aiMessage = `echo "
20878
20878
  ================================================================================
20879
- \uD83D\uDEAB COMMIT BLOCKED BY SONARQUBE
20879
+ \uD83D\uDEAB COMMIT BLOCKED - SonarQube Quality Gate Failed
20880
20880
  ================================================================================
20881
20881
 
20882
- WHAT IS SONARQUBE?
20883
- SonarQube is a code quality tool that analyzes your code for bugs, vulnerabilities,
20884
- security issues, and code smells. This project has pre-commit blocking enabled,
20885
- which means commits are blocked if the code quality is not good enough.
20882
+ STOP! Your commit was blocked. DO NOT:
20883
+ Delete opencode.json
20884
+ Remove plugins
20885
+ Retry without fixing issues
20886
20886
 
20887
- WHY WAS THIS BLOCKED?
20888
- Your commit was blocked because the SonarQube quality gate FAILED. This means
20889
- there are code quality issues that need to be fixed before you can commit.
20887
+ ================================================================================
20888
+ \uD83D\uDCCB YOU HAVE A SONARQUBE TOOL - USE IT!
20889
+ ================================================================================
20890
+
20891
+ You have access to the 'sonarqube' MCP tool (same as mcp_sonarqube).
20892
+ Call it NOW to see exactly what issues are blocking you:
20890
20893
 
20891
- HOW TO FIX THIS:
20894
+ sonarqube({ action: 'issues' }) ← CALL THIS TOOL NOW!
20892
20895
 
20893
- Step 1: See what issues were found
20894
- Use the sonarqube tool to view the issues:
20895
- sonarqube({ action: 'issues' })
20896
+ This tool will show you:
20897
+ - Every issue found in the code
20898
+ - The file and line number
20899
+ - The severity (BLOCKER/CRITICAL/MAJOR/MINOR/INFO)
20900
+ - Description of what's wrong
20901
+ - How to fix it
20896
20902
 
20897
- Step 2: Understand the issues
20898
- Each issue shows:
20899
- - Severity (BLOCKER, CRITICAL, MAJOR, MINOR, INFO)
20900
- - The file and line number
20901
- - A description of the problem
20902
- - Often a suggestion for how to fix it
20903
+ Other useful tool calls:
20904
+ sonarqube({ action: 'status' }) See why quality gate failed
20905
+ sonarqube({ action: 'analyze' }) ← Re-run analysis after fixes
20903
20906
 
20904
- Step 3: Fix the issues in your code
20905
- Edit the files to resolve the issues. Common issues include:
20906
- - Hardcoded passwords or API keys
20907
- - SQL injection vulnerabilities
20908
- - Unused variables
20909
- - Code duplication
20910
- - Missing null checks
20907
+ ================================================================================
20908
+ WHAT TO DO NOW:
20909
+ ================================================================================
20911
20910
 
20912
- Step 4: Try committing again
20913
- After fixing the issues, try your commit again.
20911
+ 1. CALL THE TOOL: sonarqube({ action: 'issues' })
20912
+ 2. READ the issues it returns
20913
+ 3. FIX the code problems
20914
+ 4. THEN try to commit again
20914
20915
 
20915
- USEFUL SONARQUBE COMMANDS:
20916
- - sonarqube({ action: 'issues' }) - See all issues
20917
- - sonarqube({ action: 'issues', severity: 'critical' }) - See critical+ issues only
20918
- - sonarqube({ action: 'analyze' }) - Re-run analysis
20919
- - sonarqube({ action: 'status' }) - Check quality gate status
20916
+ The quality gate may fail due to issues in existing code, not just your changes.
20917
+ Use sonarqube({ action: 'status' }) to see what conditions failed.
20920
20918
 
20921
- IMPORTANT: Do NOT retry the commit without fixing the issues first!
20922
20919
  ================================================================================
20923
20920
  " && exit 1`;
20924
20921
  args.command = aiMessage;
@@ -20932,36 +20929,43 @@ IMPORTANT: Do NOT retry the commit without fixing the issues first!
20932
20929
  if (result.block && args) {
20933
20930
  const aiMessage = `echo "
20934
20931
  ================================================================================
20935
- \uD83D\uDEAB PUSH BLOCKED BY SONARQUBE
20932
+ \uD83D\uDEAB PUSH BLOCKED - SonarQube Quality Gate Failed
20936
20933
  ================================================================================
20937
20934
 
20938
- WHAT IS SONARQUBE?
20939
- SonarQube is a code quality tool that analyzes your code for bugs, vulnerabilities,
20940
- security issues, and code smells. This project has pre-push blocking enabled,
20941
- which means pushes are blocked if the code quality is not good enough.
20935
+ STOP! Your push was blocked. DO NOT:
20936
+ Delete opencode.json
20937
+ Remove plugins
20938
+ Retry without fixing issues
20942
20939
 
20943
- WHY WAS THIS BLOCKED?
20944
- Your push was blocked because the SonarQube quality gate FAILED. This means
20945
- there are code quality issues that need to be fixed before you can push.
20940
+ ================================================================================
20941
+ \uD83D\uDCCB YOU HAVE A SONARQUBE TOOL - USE IT!
20942
+ ================================================================================
20946
20943
 
20947
- HOW TO FIX THIS:
20944
+ You have access to the 'sonarqube' MCP tool (same as mcp_sonarqube).
20945
+ Call it NOW to see exactly what issues are blocking you:
20948
20946
 
20949
- Step 1: See what issues were found
20950
- sonarqube({ action: 'issues' })
20947
+ sonarqube({ action: 'issues' }) ← CALL THIS TOOL NOW!
20951
20948
 
20952
- Step 2: Fix the issues in your code
20949
+ This tool will show you:
20950
+ - Every issue found in the code
20951
+ - The file and line number
20952
+ - The severity (BLOCKER/CRITICAL/MAJOR/MINOR/INFO)
20953
+ - Description of what's wrong
20953
20954
 
20954
- Step 3: Commit your fixes
20955
- git add . && git commit -m 'fix: resolve code quality issues'
20955
+ Other useful tool calls:
20956
+ sonarqube({ action: 'status' }) ← See why quality gate failed
20957
+ sonarqube({ action: 'analyze' }) ← Re-run analysis after fixes
20956
20958
 
20957
- Step 4: Try pushing again
20959
+ ================================================================================
20960
+ ⚡ WHAT TO DO NOW:
20961
+ ================================================================================
20958
20962
 
20959
- USEFUL SONARQUBE COMMANDS:
20960
- - sonarqube({ action: 'issues' }) - See all issues
20961
- - sonarqube({ action: 'analyze' }) - Re-run analysis
20962
- - sonarqube({ action: 'status' }) - Check quality gate status
20963
+ 1. CALL THE TOOL: sonarqube({ action: 'issues' })
20964
+ 2. READ the issues it returns
20965
+ 3. FIX the code problems
20966
+ 4. Commit your fixes
20967
+ 5. THEN try to push again
20963
20968
 
20964
- IMPORTANT: Do NOT retry the push without fixing the issues first!
20965
20969
  ================================================================================
20966
20970
  " && exit 1`;
20967
20971
  args.command = aiMessage;
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "opencode-sonarqube",
3
- "version": "1.2.32",
3
+ "version": "1.2.34",
4
4
  "description": "OpenCode Plugin for SonarQube integration - Enterprise-level code quality from the start",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",