Skip to content

Fix release branch resolution picking stale feature branches #886

Fix release branch resolution picking stale feature branches

Fix release branch resolution picking stale feature branches #886

Triggered via pull request July 20, 2026 07:13
Status Failure
Total duration 1m 1s
Artifacts

pr.yml

on: pull_request
Check Commit Message
6s
Check Commit Message
Test
58s
Test
Run spellcheck
5s
Run spellcheck
Fit to window
Zoom out
Zoom in

Annotations

1 error and 4 warnings
Check Commit Message
Error: One of your your commit messages is not matching the format with JIRA ID Ex: ( SDK-123 commit message )
Run spellcheck
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Check Commit Message
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: gsactions/commit-message-checker@v1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/setup-java@v1, codecov/codecov-action@v2.1.0, jsdaniell/create-json@1.1.2. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/