Update Coverity to run on main and release branches

[azwolski]

Description

The change was reverted due to the following error:

parse error: Invalid numeric literal at line 2, column 0
Error: Process completed with exit code 4.

However, the failure continued to occur even after the revert, which indicates that the issue was not caused by this PR.

Timeline

• PR Remove hardcoded trunk from yaml and script files #3725 was merged on Jan 28, 2026
• The first failure occurred on Jan 30, 11:02 PM (GMT+1)
• The commit was reverted on Feb 4
• The failure was still present as of Feb 12, 11:05 PM (GMT+1)

Since the error persisted after the revert, the original change does not appear to be the root cause and should be restored.

Related Issue

• [CI] Some of the jobs are failing on release branches #3681

Checklist

• Code has been formatted with clang-format (e.g., clang-format -i src/ispc.cpp)
• Git history has been squashed to meaningful commits (one commit per logical change)
• Compiler changes are covered by lit tests
• Language/stdlib changes include new functional tests for runtime behavior
• Documentation updated if needed

[Copilot]

Pull request overview

This pull request restores a previously reverted change that updates the Coverity static analysis workflow to run on both the main branch and release branches. The original change (PR #3725) was reverted due to an error that was later determined to be unrelated to the change, as the error persisted even after the revert.

Changes:

• Updated the COVERITY_SCAN_BRANCH_PATTERN environment variable to match both "main" and branches starting with "releases/"
• This allows Coverity scans to run on release branches in addition to the main branch

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[dbabokin]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Nice work!

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[dbabokin]

LGTM

And again - would be good to fix zizmor error.