-
Notifications
You must be signed in to change notification settings - Fork 163
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
actions/download-artifact for GHE environment #468
Comments
Same for artifact-upload |
I have no idea because I don't have a GHE environment with GitHub Actions enabled. One obvious workaround for this is ignoring the erorr by regular expressions as desribed in the v1.7.4 releae note. Before considering to add some special handling for this, I'd like to ask some questions to understand the situation better.
I'm a bit confused because they announce that |
I found |
Cool. What we have done temporarily is to use the commit hash pointing to the current v3 (at the expense of maybe failing to keep up to the date with v3 patches). I didn't know about the
There's some info related to roadmap here actions/upload-artifact#537 - tl;dr v3 will be deprecated but will still run on GHES moving forward, with the expectation that v4 will be supported Q1 2025
Not sure what you mean. On GHES you only have self-hosted runners AFAIK, so anything goes. |
Yeah, I don't know how it is maintained. However
Thank you for the information. Then I believe
I didn't know that GHES only supports self-hosted runners. As I said above, I don't have GHES environment hence I don't know the specs at all. Thanks for explaining that 👍 |
I'm closing this because |
using v3 fails actionlint with
but actions/upload-artifact@v4 cannot be used on GHES
Can we add a special condition?
The text was updated successfully, but these errors were encountered: