Upgrade GitHub Actions to latest versions

[salmanmkc]

Summary

Upgrade GitHub Actions to their latest versions for improved features, bug fixes, and security updates.

Changes

Action	Old Version(s)	New Version	Release	Files
abatilo/actions-poetry	v2	v3	Release	ai-service-release-stable-image.yaml
actions/create-github-app-token	v1	v2	Release	ai-service-release-stable-image.yaml, ui-release-image-stable.yaml
extractions/setup-just	v2	v3	Release	ai-service-test.yaml
golangci/golangci-lint-action	v8	v9	Release	wren-launcher-ci.yaml
kontrolplane/pull-request-title-validator	v1.3.1	v1.5.0	Release	pull-request-title-validator.yaml
peter-evans/create-pull-request	v7	v8	Release	create-rc-release-pr.yaml
tj-actions/changed-files	v46	v47	Release	pr-tagger.yaml

Why upgrade?

Keeping GitHub Actions up to date ensures:

• Security: Latest security patches and fixes
• Features: Access to new functionality and improvements
• Compatibility: Better support for current GitHub features
• Performance: Optimizations and efficiency improvements

Security Note

Actions that were previously pinned to commit SHAs remain pinned to SHAs (updated to the latest release SHA) to maintain the security benefits of immutable references.

Testing

These changes only affect CI/CD workflow configurations and should not impact application functionality. The workflows should be tested by running them on a branch before merging.

Summary by CodeRabbit

• Chores
  • Updated automation and CI/CD workflow tooling to newer versions across multiple pipelines.
  • Infrastructure updates improve system stability, security posture, and compatibility with latest standards.

[coderabbitai]

Walkthrough

This PR updates the versions of multiple GitHub Actions and external tools used across various CI/CD workflows, including bumps to GitHub app token creation, Poetry, golangci-lint, changed-files detection, PR management, and title validation actions.

Changes

Cohort / File(s)	Summary
GitHub App Token Generation .github/workflows/ai-service-release-stable-image.yaml, .github/workflows/ui-release-image-stable.yaml	Upgraded actions/create-github-app-token from v1 to v2 in both workflows.
CI/CD Tool Upgrades .github/workflows/ai-service-release-stable-image.yaml	Updated abatilo/actions-poetry from v2 to v3.
Development & Linting Tools .github/workflows/ai-service-test.yaml, .github/workflows/wren-launcher-ci.yaml	Bumped Just installer from v2 to v3 and golangci-lint action from v8 to v9 respectively.
Workflow Action Updates .github/workflows/create-rc-release-pr.yaml, .github/workflows/pr-tagger.yaml, .github/workflows/pull-request-title-validator.yaml	Upgraded peter-evans/create-pull-request from v7 to v8, tj-actions/changed-files from v46 to v47, and kontrolplane/pull-request-title-validator from v1.3.1 to v1.5.0.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• fix release-rc-pr workflow #1487: Introduced prior modifications to the create-rc-release-pr.yaml workflow and previously updated the peter-evans/create-pull-request action version.
• chore(wren-ui): change base image and optimize docker build #1029: Previously modified the ui-release-image-stable.yaml workflow and the tag-ui-version job that receives the GitHub App token action update.

Suggested reviewers

• wwwy3y3
• grieve54706
• cyyeh

Poem

🐰 Our workflows hop to newer ground,
Action versions spinning all around,
From v1 to v2, v8 to v9,
Each tool updated—things run just fine!
Dependency bumps with careful care,
CI/CD excellence in the air! ✨

🚥 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	The title 'Upgrade GitHub Actions to latest versions' accurately and specifically summarizes the main change across all modified files in the pull request.
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

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In @.github/workflows/create-rc-release-pr.yaml:
- Line 68: The workflow uses the action "uses:
peter-evans/create-pull-request@v8" which requires Node 24 on the runner; if you
use self-hosted runners, verify and document that they are running Actions
Runner v2.327.1 or later (or upgrade them) so the v8 action runs properly—update
repository CONTRIBUTING/CI docs or add a README note referencing the workflow
action string to inform maintainers to check/upgrade self-hosted runner
versions.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🌐 Web query:

peter-evans/create-pull-request v8 breaking changes release notes

💡 Result:

peter-evans/create-pull-request v8 — breaking / required changes (release notes)

• Self-hosted runners must be updated: if you run this action on a self-hosted GitHub Actions runner, you need Actions Runner v2.327.1+ to ensure Node 24 support (which v8 uses). Otherwise the action may fail to run. [1][3]
• actions/checkout updated to v6 inside the project (and docs updated accordingly). If your workflows (or enterprise policies) pin/allow only older actions/checkout major versions, review compatibility. [1]

No other explicit input/output “behaviour changes” are called out in the v8.0.0 release notes beyond the runner/Node 24 requirement and the checkout major bump. [1][2]

Sources: [1] [2] [3]

---

All inputs (base, branch, commit-message, title, body, draft) are compatible with v8—no breaking changes for input parameters.

However, if this repository uses self-hosted GitHub Actions runners, verify they are running Actions Runner v2.327.1 or later to support Node 24 (required by v8). GitHub-hosted runners are unaffected.

🤖 Prompt for AI Agents

In @.github/workflows/create-rc-release-pr.yaml at line 68, The workflow uses
the action "uses: peter-evans/create-pull-request@v8" which requires Node 24 on
the runner; if you use self-hosted runners, verify and document that they are
running Actions Runner v2.327.1 or later (or upgrade them) so the v8 action runs
properly—update repository CONTRIBUTING/CI docs or add a README note referencing
the workflow action string to inform maintainers to check/upgrade self-hosted
runner versions.