[GH-ISSUE #2472] Make --use-new-action-cache the new default for downloading actions #1142

Closed
opened 2026-03-01 21:49:14 +03:00 by kerem · 4 comments
Owner

Originally created by @ChristopherHX on GitHub (Sep 26, 2024).
Original GitHub issue: https://github.com/nektos/act/issues/2472

  • #2471
  • deprecate the old
    • migrate tests
  • ask for cleanup of all folders used by old action cache
  • plan removal of the old, breaking for act_runner, gh-act-runner
Originally created by @ChristopherHX on GitHub (Sep 26, 2024). Original GitHub issue: https://github.com/nektos/act/issues/2472 - #2471 - deprecate the old - migrate tests - ask for cleanup of all folders used by old action cache - plan removal of the old, breaking for act_runner, gh-act-runner
Author
Owner

@ChristopherHX commented on GitHub (Nov 3, 2024):

Ask for cleanup has been discarded

old cache names use an @ symbol, new cache entries no longer have that part

<!-- gh-comment-id:2453238523 --> @ChristopherHX commented on GitHub (Nov 3, 2024): Ask for cleanup has been discarded old cache names use an `@` symbol, new cache entries no longer have that part
Author
Owner

@ChristopherHX commented on GitHub (Feb 4, 2025):

Abandoning

<!-- gh-comment-id:2634827092 --> @ChristopherHX commented on GitHub (Feb 4, 2025): Abandoning
Author
Owner

@snowflyak commented on GitHub (Feb 5, 2025):

@ChristopherHX, are you abandoning the immediate plan to switch to new action cache by default or the whole idea of replacing the cache engine implementation? Is this due to having come up a better solution or because of lack of time/interest?

<!-- gh-comment-id:2635947518 --> @snowflyak commented on GitHub (Feb 5, 2025): @ChristopherHX, are you abandoning the immediate plan to switch to new action cache by default or the whole idea of replacing the cache engine implementation? Is this due to having come up a better solution or because of lack of time/interest?
Author
Owner

@ChristopherHX commented on GitHub (Feb 5, 2025):

are you abandoning the immediate plan to switch to new action cache by default or the whole idea of replacing the cache engine implementation?

I am abandoning both for nektos/act only1

Is this due to having come up a better solution or because of lack of time/interest?

Due to lack of time/interest of reviewers no comments within a 2 month timeframe in my PR that implements every point mentioned in this issue.

If you are able to involve cplee or wolfogre (on of them is required for a merge of my changes) this can be reconsidered from my point of view for nektos/act.


  1. I have settled with a code split of the whole project for now, where I'm an owner.
    Released in actions-oss/act-cli v0.3.0 / 1. February 2025 ↩︎

<!-- gh-comment-id:2636401787 --> @ChristopherHX commented on GitHub (Feb 5, 2025): > are you abandoning the immediate plan to switch to new action cache by default or the whole idea of replacing the cache engine implementation? I am abandoning both for nektos/act only[^1] > Is this due to having come up a better solution or because of lack of time/interest? Due to lack of time/interest of reviewers no comments within a 2 month timeframe in my PR that implements every point mentioned in this issue. If you are able to involve cplee or wolfogre (on of them is required for a merge of my changes) this can be reconsidered from my point of view for nektos/act. [^1]: I have settled with a code split of the whole project for now, where I'm an owner. Released in actions-oss/act-cli v0.3.0 / 1. February 2025
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/act#1142
No description provided.