Fix blackduck

[lisajulia]

Fix BlackDuck CI Configuration and Dependency Updates

🔧 Chore: Cleaned up the BlackDuck scan action by removing unnecessary github_token input, and updated several dependency versions in the Maven build files.

Changes

• .github/actions/scan-with-blackduck/action.yml: Removed the github_token input parameter and its usage in the BlackDuck Security Scan step. Also fixed indentation in the detect_args block.
• .github/workflows/main.yml: Removed the github_token reference passed to the BlackDuck scan action.
• pom.xml: Updated software.amazon.awssdk-s3-version from 2.42.33 to 2.44.11, bumped com.sap.cloud.sdk:sdk-bom from 5.27.0 to 5.30.0
• added io.netty:netty-bom version 4.2.14.Final to the dependency management section.
• storage-targets/cds-feature-attachments-oss/pom.xml: Updated azure-storage-blob from 12.33.3 to 12.34.0 and google-cloud-storage from 2.66.0 to 2.68.0.

• 🔄 Regenerate and Update Summary

PR Bot Information

Version: 1.21.0

• Summary Prompt: Default Prompt
• Correlation ID: e5b1fa3d-8b5d-4d04-aa40-a7fd907e4a7d
• Event Trigger: pull_request.edited
• LLM: anthropic--claude-4.6-sonnet
• Output Template: Default Template
• File Content Strategy: Full file content

[hyperspace-insights]

The PR is a minimal and clean fix that removes the now-unused github_token input from the composite action and its callers, and adds a RAPID-mode BlackDuck scan job to the PR workflow. One issue was flagged: the pinned SHA for actions/checkout carries an incorrect # v6 version comment — it should be # v4.

PR Bot Information

Version: 1.21.0

• LLM: anthropic--claude-4.6-sonnet
• Event Trigger: pull_request.opened
• Correlation ID: 9727e100-69ac-446f-85bd-c67c7a897046
• File Content Strategy: Full file content
• Agent Instructions:
  • CLAUDE.md

[lisajulia]

@Schmarvinius: Can you have a look at this? Here, the blackduck scan passes: https://github.com/cap-java/cds-feature-attachments/actions/runs/26522023089/job/78115440499.
Also: We could run the blackduck scan in rapid mode on PRs, then that can be compared to the last run on main which was persisted. We can even tell Blackduck to compare against the last saved scan and check if new vulnerabilites were added: https://documentation.blackduck.com/bundle/detect/page/runningdetect/rapidscan.html#rapid-scan-compare-mode.
In any case, we still have to monitor the scans on main.