Skip to content

Conversation

@snyk-abedonik
Copy link

Pull Request Submission Checklist

  • Follows CONTRIBUTING guidelines
  • Commit messages
    are release-note ready, emphasizing
    what was changed, not how.
  • Includes detailed description of changes
  • Contains risk assessment (Low | Medium | High)
  • Highlights breaking API changes (if applicable)
  • Links to automated tests covering new functionality
  • Includes manual testing instructions (if necessary)
  • Updates relevant GitBook documentation (PR link: ___)
  • Includes product update to be announced in the next stable release notes

What does this PR do?

Where should the reviewer start?

How should this be manually tested?

What's the product update that needs to be communicated to CLI users?

@github-actions
Copy link
Contributor

github-actions bot commented Jan 3, 2026

Your PR has not had any activity for 30 days. In 2 days I'll close it. Make some activity to remove this.

@github-actions github-actions bot added the Stale label Jan 3, 2026
@github-actions
Copy link
Contributor

github-actions bot commented Jan 5, 2026

Your PR has now been stale for 2 days. I'm closing it.

@github-actions github-actions bot closed this Jan 5, 2026
@github-actions github-actions bot deleted the feat/CSENG-37-maven-scope-in-sbom-early-access branch January 5, 2026 00:35
@snyk-abedonik snyk-abedonik restored the feat/CSENG-37-maven-scope-in-sbom-early-access branch January 12, 2026 18:01
@snyk-abedonik snyk-abedonik reopened this Jan 12, 2026
@snyk-abedonik snyk-abedonik force-pushed the feat/CSENG-37-maven-scope-in-sbom-early-access branch from 92f66d6 to 8097547 Compare January 12, 2026 18:17
@snyk snyk deleted a comment from github-actions bot Jan 12, 2026
@github-actions
Copy link
Contributor

github-actions bot commented Jan 15, 2026

Fails
🚫

"feat(CSENG-37): maven build scope in sbom early access" is not using a valid commit message format. For commit guidelines, see: CONTRIBUTING.

🚫

"fix(CSENG-37): missing npm scope when --all-projects specified" is not using a valid commit message format. For commit guidelines, see: CONTRIBUTING.

🚫

"feat(CSENG-37): enable npm scope in sbom early access" is not using a valid commit message format. For commit guidelines, see: CONTRIBUTING.

🚫

"feat(CSENG-37): maven build scope in sbom early access" is not using a valid commit message format. For commit guidelines, see: CONTRIBUTING.

Warnings
⚠️

Since the CLI is unifying on a standard and improved tooling, we're starting to migrate old-style imports and exports to ES6 ones.
A file you've modified is using either module.exports or require(). If you can, please update them to ES6 import syntax and export syntax.
Files found:

  • src/lib/plugins/get-single-plugin-result.ts
  • src/lib/plugins/nodejs-plugin/npm-workspaces-parser.ts
  • src/lib/plugins/nodejs-plugin/yarn-workspaces-parser.ts
⚠️

You've modified files in src/ directory, but haven't updated anything in test folder. Is there something that could be tested?

⚠️ There are multiple commits on your branch, please squash them locally before merging!

Generated by 🚫 dangerJS against 1039fc1

@snyk-abedonik snyk-abedonik force-pushed the feat/CSENG-37-maven-scope-in-sbom-early-access branch from f4531e6 to 1039fc1 Compare January 15, 2026 20:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants