Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request]: Upgrade actions/cache to v4 #5601

Open
BenHenning opened this issue Dec 18, 2024 · 1 comment · May be fixed by #5603
Open

[Feature Request]: Upgrade actions/cache to v4 #5601

BenHenning opened this issue Dec 18, 2024 · 1 comment · May be fixed by #5603
Assignees
Labels
enhancement End user-perceivable enhancements. Impact: High High perceived user impact (breaks a critical feature or blocks a release). triage needed

Comments

@BenHenning
Copy link
Member

Is your feature request related to a problem? Please describe.

Per https://github.blog/changelog/2024-09-16-notice-of-upcoming-deprecations-and-changes-in-github-actions-services/ actions v1 and v2 are deprecated and will soon result in workflow failures.

Describe the solution you'd like

All workflows that use actions/cache should be upgraded to v4.

Describe alternatives you've considered

We must perform this upgrade, though we could technically upgrade to v3, instead (however, since we infrequently perform this upgrades it seems more forward-looking to move straight to v4).

Additional context

No response

@BenHenning BenHenning added enhancement End user-perceivable enhancements. triage needed Impact: High High perceived user impact (breaks a critical feature or blocks a release). labels Dec 18, 2024
@BenHenning
Copy link
Member Author

NB: This is high impact because if we don't fix it we will end up with failing workflows.

@manas-yu manas-yu self-assigned this Dec 18, 2024
@manas-yu manas-yu linked a pull request Dec 18, 2024 that will close this issue
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement End user-perceivable enhancements. Impact: High High perceived user impact (breaks a critical feature or blocks a release). triage needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants