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

Make --use-new-action-cache the new default for downloading actions #2472

Closed
ChristopherHX opened this issue Sep 26, 2024 · 4 comments
Closed
Labels
area/runner Relating to errors in the runner kind/feature-request New feature or request size/XL

Comments

@ChristopherHX
Copy link
Contributor

@ChristopherHX ChristopherHX added kind/feature-request New feature or request area/runner Relating to errors in the runner backlog Those issues are on the roadmap size/XL labels Sep 26, 2024
@ChristopherHX ChristopherHX linked a pull request Oct 29, 2024 that will close this issue
@ChristopherHX
Copy link
Contributor Author

Ask for cleanup has been discarded

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

@ChristopherHX
Copy link
Contributor Author

Abandoning

@ChristopherHX ChristopherHX closed this as not planned Won't fix, can't repro, duplicate, stale Feb 4, 2025
@ChristopherHX ChristopherHX removed the backlog Those issues are on the roadmap label Feb 4, 2025
@snowflyak
Copy link

@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?

@ChristopherHX
Copy link
Contributor Author

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.

Footnotes

  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 up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/runner Relating to errors in the runner kind/feature-request New feature or request size/XL
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants