Repository navigation
ci: pin .github callers to v4.7.0 - #367
Conversation
Part of DevSecNinja/repo-steward#73 (batch 4). Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
There was a problem hiding this comment.
🟢 Approval recommended
The Config Sync workflow update has no active review issues.
No open issues 🎉
What changed in this PR
Updates Wazzup’s Config Sync workflow to the shared .github v4.7.0 release, addressing #366’s upgrade for signed sync commits, create-only Renovate configuration, and scripts fetched from the pinned commit.
Changes:
- Advances the reusable workflow pin from v1.9.0 to v4.7.0.
- Explicitly forwards
AUTOMATION_APP_PRIVATE_KEYwhile retaining existing permissions.
| File | Description |
|---|---|
.github/workflows/config-sync.yml |
Updates the shared workflow pin and passes the automation app private-key secret. |
Review effort: Balanced
Closes #366
Changes
.github/workflows/config-sync.yml: pin to v4.7.0 (231c380d4f75486e159ed2e3d806bc76ff193a43).release-please.ymlkeeps the interface it has had since v3.4.0.config-sync.ymlkeeps the same inputs, secrets and permissions. Since v4.x it checks out withpersist-credentials: false, commits through the GitHub API (signed by GitHub), treatsrenovate.json5as create-only, and in v4.7.0 runs its scripts from the pinned.githubcommit. The sync warns whilerenovate.json5doesn't extendgithub>DevSecNinja/.github//.renovate/default.json5(DevSecNinja/.github#513).Post-merge check
renovate.json5.Part of DevSecNinja/repo-steward#73 (batch 4, owner-approved). Opened by repo-steward through the GitHub API; the commit is signed by GitHub (
createCommitOnBranch).Summary by CodeRabbit