[Bornunique911]

Summary

This PR is a follow-up to #1105, which was merged into staging. The workflow files on staging still carry runs-on: ubuntu-latest and python-version: '3.12', so CI fails at the "Set up Python" step.

This PR applies the same minimal CI fix that #1201 applied to main, but targets staging so that runs on staging are unblocked and the environment matches the documented Python requirement.

Problem Fixed

Both test.yml and e2e.yml on staging fail before any test step can run:

• runs-on: ubuntu-latest, which GitHub has migrated to Ubuntu 26.04, and
• python-version: '3.12', which has no prebuilt binary for Ubuntu 26.04 in the actions/setup-python manifest.

The job fails at the "Set up Python" step with an error of the form:

Error: The version '3.12' with architecture 'x64' was not found for Ubuntu 26.04.

This blocked CI for #1105 and any branch based on staging.

Solution

Two minimal changes in each workflow file on staging:

File	Change
.github/workflows/e2e.yml	runs-on: ubuntu-latest → ubuntu-24.04; python-version: '3.12' → '3.11'
.github/workflows/test.yml	runs-on: ubuntu-latest → ubuntu-24.04; python-version: '3.12' → '3.11'

Why ubuntu-24.04: pins the job to a stable runner image where Python 3.11 builds are available, and prevents future ubuntu-latest migrations from silently breaking CI on staging again.

Why 3.11: matches the project's documented requirement. .python-version contains exactly 3.11.9, and README.md states installation requires Python 3.11.9. Requesting the minor version ('3.11') lets setup-python resolve to the latest 3.11 patch from the runner cache, rather than pinning a patch that could disappear from the manifest.

Diff

# .github/workflows/test.yml and .github/workflows/e2e.yml
- runs-on: ubuntu-latest
+ runs-on: ubuntu-24.04

- python-version: '3.12'
+ python-version: '3.11'

Tests

• Diff is limited to the two workflow files (2 files changed, 4 insertions(+), 4 deletions(-)).
• CI on this PR reaches the actual test steps instead of failing at environment setup.
• The "Set up Python" step succeeds because Python 3.11 has a build for ubuntu-24.04.

Reviewer Notes

• No application code touched — the importer fixtures and parser tests from Fix OWASP importer hyperlinks #1105 are untouched.
• No Node.js version change — the existing node-version in e2e.yml is left as-is to keep the fix scoped.
• No action major-version bumps — actions/checkout@v4, setup-python@v5, setup-node@v4, and upload-artifact@v4 are preserved.
• Branch target — opened against staging, not main, because Fix OWASP importer hyperlinks #1105 landed on staging and its workflow files still carry the broken pins.

Related

• Follow-up to #1105
• Mirrors #1201 (applied to main)
• CI context: #952, #1197

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

🗂️ Base branches to auto review: 1

• main

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: OWASP/OpenCRE
• Branch: staging
• File: .coderabbit.yml
• Commit: 1f327ad
• Layers: Repository YAML
• Review profile: CHILL
• Plan: Advanced
• Run ID: 32dbe693-6ed3-430f-9526-1fadfef425c0

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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