Skip to content

feat: release時にmanifestのRenovateを回すようにする - #1047

Open
renkonmaster wants to merge 1 commit into
masterfrom
feat/run-manifest-renovate
Open

feat: release時にmanifestのRenovateを回すようにする#1047
renkonmaster wants to merge 1 commit into
masterfrom
feat/run-manifest-renovate

Conversation

@renkonmaster

@renkonmaster renkonmaster commented Feb 23, 2026

Copy link
Copy Markdown

Release時にmanifestのRenovateを動かすようにGHAを書いた

Summary by CodeRabbit

リリースノート

  • Chores
    • リリースワークフローを改善し、自動化プロセスを拡張しました。

@coderabbitai

coderabbitai Bot commented Feb 23, 2026

Copy link
Copy Markdown
📝 Walkthrough

Walkthrough

GitHub Actionsのrelease.yamlワークフローに新しいジョブ「Run Renovate on manifest」を追加しました。このジョブは画像ビルド後に実行され、GitHub APIを通じて別のリポジトリのワークフローをトリガーします。

Changes

Cohort / File(s) Summary
GitHub Actions ワークフロー
.github/workflows/release.yaml
imageジョブに依存する新しい「Run Renovate on manifest」ジョブを追加。contents:readactions:writeのパーミッションを設定し、PAT_TOKENを使用してtraPtitech/manifestリポジトリのrenovate.yamlワークフローをdispatchするGitHub APIコールを実行します。

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed PRタイトル「feat: release時にmanifestのRenovateを回すようにする」は、変更内容(Release時にmanifestリポジトリのRenovateワークフローをディスパッチするGitHub Actionsジョブを追加)と完全に合致しており、主要な変更を明確に要約している。
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch feat/run-manifest-renovate

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (1)
.github/workflows/release.yaml (1)

74-74: releaseジョブへの依存も検討を

現在は needs: [image] のみで、releaseジョブ(GitHub Releaseの作成)が成功しているかどうかに関わらず、imageジョブが成功すればRenovateが起動します。PR目的が「Release時にRenovateを回す」であれば、releaseジョブの成功も条件に含めることを検討してください。

♻️ 修正案
-    needs: [image]
+    needs: [image, release]
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.github/workflows/release.yaml at line 74, The job currently lists only
needs: [image], so Renovate can run even if the release job failed; update the
job's needs array to include the release job as a dependency (e.g., change
needs: [image] to needs: [image, release]) so that the job waits for both the
image and release jobs to succeed; locate the job definition in release.yaml and
modify the needs key accordingly.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.github/workflows/release.yaml:
- Around line 76-78: Remove the unnecessary elevated workflow permission by
deleting the "actions: write" entry from the permissions block (leave "contents:
read"), since the job overrides GITHUB_TOKEN with env GITHUB_TOKEN: ${{
secrets.PAT_TOKEN }} and therefore does not use the built-in token; update the
permissions stanza (referencing the permissions: block and the actions: write
symbol) to follow least-privilege.

---

Nitpick comments:
In @.github/workflows/release.yaml:
- Line 74: The job currently lists only needs: [image], so Renovate can run even
if the release job failed; update the job's needs array to include the release
job as a dependency (e.g., change needs: [image] to needs: [image, release]) so
that the job waits for both the image and release jobs to succeed; locate the
job definition in release.yaml and modify the needs key accordingly.

ℹ️ Review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7ad2a56 and 4bf7069.

📒 Files selected for processing (1)
  • .github/workflows/release.yaml

Comment thread .github/workflows/release.yaml
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant