Conversation
Bumps the security-scanners group with 1 update: [trufflesecurity/trufflehog](https://github.com/trufflesecurity/trufflehog). Updates `trufflesecurity/trufflehog` from 3.95.9 to 3.96.0 - [Release notes](https://github.com/trufflesecurity/trufflehog/releases) - [Commits](trufflesecurity/trufflehog@27b0417...6f3c981) --- updated-dependencies: - dependency-name: trufflesecurity/trufflehog dependency-version: 3.96.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: security-scanners ... Signed-off-by: dependabot[bot] <support@github.com>
Add an announce_release job to release.yml that calls release-notification.yml after a successful release, routing the announcement per repository: channel from announcement_slack_channel or the RELEASE_SLACK_CHANNEL variable, webhook from the RELEASE_WEBHOOK_URL secret (RELEASE_WEBHOOK_NOTIFICATION_URL kept as fallback). The job is skipped when no channel is configured and the notification step is skipped when the webhook secret is absent. release-notification.yml gains an optional release_tag input so the umbrella announces the tag actually published by the run instead of the newest release in the repository, which was wrong for monorepo matrix legs. go-release.yml and js-release.yml expose the three new inputs and pass them through to release.yml. Discord is not wired into the umbrella job: SethCohen/github-releases-to-discord reads the release event payload, absent on the push event that drives release.yml. Discord announcements stay on a dedicated on: release caller.
The Discord and Slack release composites were pinned to @v1.18.0, which the pinned-actions lint flags: internal composites must use the floating major tag (@vn) while internal reusable workflows use an exact version. Aligns both refs with the rest of the repository.
CodeQL flagged the dry-run summary step for interpolating product_name, slack_channel and the resolved release tag straight into the run block. Every value now reaches bash as an environment variable, and the discord/slack enable flags are computed in shell instead of via expression interpolation.
… the security-scanners group (#616) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Summary by CodeRabbit
WalkthroughChangesThe reusable release workflows now support configurable Slack announcements and release-tag overrides. GitOps Kustomize tagging supports per-artifact image mappings with fallback behavior. Related documentation and the TruffleHog action version are also updated. Kustomize image routing
Release announcements
Security action update
Estimated code review effort: 4 (Complex) | ~45 minutes Possibly related PRs
Suggested labels: Suggested reviewers: 🚥 Pre-merge checks | ✅ 3 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (3 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
🔍 PR Validation Summary✅ PR Mergeable — no blocking failures
|
🔍 Lint Analysis
|
🛡️ CodeQL Analysis ResultsLanguages analyzed: Found 2 issue(s): 2 Medium
🔍 View full scan logs | 🛡️ Security tab |
There was a problem hiding this comment.
Warning
CodeRabbit couldn't request changes on this pull request because it doesn't have sufficient GitHub permissions.
Please grant CodeRabbit Pull requests: Read and write permission and re-run the review.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/gitops-update-workflow.md`:
- Around line 118-121: Update the notes describing artifact resolution so they
only state the fallback for artifacts absent from the mapping when
kustomize_image_name is empty. Remove the claim that empty mapping entries are
skipped with a warning, since workflow validation rejects those values.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yml
Review profile: ASSERTIVE
Plan: Pro
Run ID: ae1697b9-419b-4241-b4e4-4299b64cb0d4
📒 Files selected for processing (11)
.github/workflows/gitops-update.yml.github/workflows/go-release.yml.github/workflows/go-security.yml.github/workflows/js-release.yml.github/workflows/release-notification.yml.github/workflows/release.ymldocs/gitops-update-workflow.mddocs/go-release-workflow.mddocs/js-release.mddocs/release-notification.mddocs/release-workflow.md
GitHub Actions Shared Workflows
Description
Type of Change
feat: New workflow or new input/output/step in an existing workflowfix: Bug fix in a workflow (incorrect behavior, broken step, wrong condition)perf: Performance improvement (e.g. caching, parallelism, reduced steps)refactor: Internal restructuring with no behavior changedocs: Documentation only (README, docs/, inline comments)ci: Changes to self-CI (workflows under.github/workflows/that run on this repo)chore: Dependency bumps, config updates, maintenancetest: Adding or updating testsBREAKING CHANGE: Callers must update their configuration after this PRBreaking Changes
None.
Testing
@this-branchor the beta tagCaller repo / workflow run:
Related Issues
Closes #