Skip to content

chore: propagate changes from main into development - #1302

Merged
Wikid82 merged 4 commits into
developmentfrom
main
Sep 7, 2026
Merged

Wikid82 merged 4 commits into
developmentfrom
main

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

Automated PR to propagate changes from main into development.

Triggered by push to main.

Wikid82 and others added 3 commits September 7, 2026 15:25
release-please cuts a release only for feat/fix/perf/deps/breaking
commits, so the recent run of chore(deps) bumps landed without a new
version.

- .github/renovate.json: semanticCommitType "deps" (scope dropped) so
  dependency PRs merge as "deps: ...", a release-triggering prefix. Two
  carve-out packageRules force CI-only tooling back to chore: — the
  github-actions manager, and custom.regex trackers under
  .github/workflows, scripts, and .github/skills (golangci-lint,
  gotestsum, govulncheck, gopls, Syft, Grype, Semgrep image, CodeQL
  CLI, NODE_VERSION/GO_VERSION). Dependencies that ship in the
  container still cut a patch release.
- CLAUDE.md: document the deps: convention and the CI-tooling carve-out.

release-please-config.json is left as-is: skip-changelog is set, so a
changelog-sections block would be inert, and deps: is release-triggering
by default without it.
@github-advanced-security

Copy link
Copy Markdown
Contributor

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

@github-actions

github-actions Bot commented Sep 7, 2026

Copy link
Copy Markdown
Contributor Author

✅ Supply Chain Verification Results

PASSED

📦 SBOM Summary

  • Components: 1769

🔍 Vulnerability Scan

Severity Count
🔴 Critical 0
🟠 High 0
🟡 Medium 0
🟢 Low 0
Total 0

📎 Artifacts

  • SBOM (CycloneDX JSON) and Grype results available in workflow artifacts

Generated by Supply Chain Verification workflow • View Details

@Wikid82
Wikid82 merged commit 5a21ef7 into development Sep 7, 2026
77 checks passed
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