Bump actions/cache from v2 to v4

[Qazi-pk]

GitHub now auto-fails any workflow using actions/cache@v2 (deprecated, cache-v2 service shut down). This is currently blocking all PRs to dev at the Set up job step, before any project code runs.

This PR bumps the three Cache conda steps in .github/workflows/ci.yml (build, test_evaluate, test_tuned jobs) from @v2 to @v4. No other changes.

Surfaced while debugging CI on #380.

[gAldeia]

Hi @Qazi-pk!

We appreciate your PR fixing this issue. Indeed, GitHub Actions is now using the @v4 version. I have already fixed this on the main branch and am working on resolving the remaining CI errors there.

I'm not sure whether the dev branch would benefit from this PR, as it is almost 500 commits behind master. I'd rather leave it untouched than risk finding new and exiting bugs to fix.

I see that you're interested in contributing a new method to SRBench, which is awesome! I'd suggest integrating it with the master branch. This way, any debugging and fixes you make will also help me, and you'll be integrating your method into the most up-to-date version of the framework.

[Qazi-pk]

Thank you for the clear guidance, and the kind words about contributing PIR. Quick clarification before I prepare the submission: the CONTRIBUTING.md in master says "In general you should submit pull requests to the dev branch," which appears to conflict with your suggestion to target master. Could you confirm which branch to target for a new-method PR? Happy to update CONTRIBUTING.md as part of the submission if the project has moved past the dev-first model. I'll close this PR (#203) and PR #380 in the meantime.

…

On Wed, 10 Jun 2026 at 01:00, Guilherme Aldeia ***@***.***> wrote: *gAldeia* left a comment (cavalab/srbench#203) <#203 (comment)> Hi @Qazi-pk <https://github.com/Qazi-pk>! We appreciate your PR fixing this issue. Indeed, GitHub Actions is now using the @v4 <https://github.com/v4> version. I have already fixed this on the main branch and am working on resolving the remaining CI errors there. I'm not sure whether the dev branch would benefit from this PR, as it is almost 500 commits behind master. I'd rather leave it untouched than risk finding new and exiting bugs to fix. I see that you're interested in contributing a new method to SRBench, which is awesome! I'd suggest integrating it with the master branch. This way, any debugging and fixes you make will also help me, and you'll be integrating your method into the most up-to-date version of the framework. — Reply to this email directly, view it on GitHub <#203?email_source=notifications&email_token=BWGIF7NRA5MWGUDEICWDQWT47BUGRA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRWGM2TENJTGE42M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4663525319>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BWGIF7K6OKDFHSVOFDKNFMD47BUGRAVCNFSM6AAAAACZWUTWJGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DMNRTGUZDKMZRHE> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/BWGIF7KO3ZQBBLPZJ7AX4ZL47BUGRA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRWGM2TENJTGE42M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/BWGIF7N35ATVLFH5I5RJIPL47BUGRA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRWGM2TENJTGE42M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

[lacava]

@gAldeia's advice is good. we need to revap dev. PR to main is okay as a stop gap.