Conversation
Adds the shared SCA scan and the solace-cloud-manifest write. Listed in the CRA Compliance product inventory (Annex A.12, Professional Services) as needing Guardian onboarding. squad is prof-services, not cto: A.12 is the Professional Services inventory, and cto would route findings into cto_vulnerabilities and file CTO Jiras. Dependencies come from: pom.xml. Scanning is read-only -- no publish, release or image step is added. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The shared SCA workflow forwards java_distribution to actions/setup-java but defaults it to an empty string, so Setup SCA Dependencies fails with "Input required and not supplied: distribution". Passing it here unblocks the scan without waiting on a fix to the shared workflow. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
A pull_request run records the scan under FOSSA branch "PR" with the branch name as the revision. Guardian looks up refs[]=<trunk_branch> and requires a hex SHA, so it cannot match those. A push to this branch has no PR number, so it takes the workflow's Manual path and registers under the default branch with the commit SHA. Temporary -- reverted once the scan has landed. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Replaces the inline manifest job with the reusable workflow now on main, and drops the temporary push trigger that was added to land a Guardian-usable FOSSA scan from this branch. The previous job ran a container pulled from this org's registry namespace, which does not exist here -- so the manifest write could not have succeeded. The reusable workflow needs no image. It also owns the default-branch check, so the caller no longer hand-writes that condition. java_distribution is no longer passed: the shared workflow's default was fixed to temurin, so an explicit value is redundant. packages: read stays -- the SCA workflow declares it, and a called workflow cannot be granted a permission the caller lacks. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…ain versions The FOSSA CLI only reads .fossa.yml from the scan root, so relocating it requires passing fossa.config explicitly via additional_scan_params -- without that the CLI silently falls back to defaults and registers the scan under a different project. Toolchain versions are now pinned rather than inherited: the shared workflow still defaults to node 20, which reached end-of-life in 2026. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
GitHub Actions parses every .yml under .github/workflows as a workflow definition, so the FOSSA config was being registered as a workflow and failing on every push. It now sits in .github/ alongside workflow-config.json, which keeps it out of the repo root without Actions trying to execute it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds FOSSA SCA scanning so this repo is covered by Solace vulnerability reporting.
.fossa.yml— FOSSA project config.github/workflow-config.json— gates inREPORTmode.github/workflows/sca-scan-and-guard.yml— calls the shared Solace SCA workflowScanning is read-only: no publish, release, image-push or deploy step, and no application code, dependency or build changes. Gates are report-only, so a finding won't fail a build.