upload-artifact@v4 does not work #144
Labels
No labels
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: forgejo/runner#144
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
https://code.forgejo.org/actions/upload-artifact@v4 does not work but https://code.forgejo.org/actions/upload-artifact@v3 does, as reported in this issue.
https://github.com/go-gitea/gitea/pull/28965 has a good high level view of the work involved.
See https://github.com/nektos/act/issues/2135
@f00 FYI
See also https://github.com/go-gitea/gitea/pull/28885
See also https://gitea.com/gitea/act_runner/pulls/473
https://github.com/go-gitea/gitea/pull/28965 sits on top of https://github.com/go-gitea/gitea/pull/28885
Forgejo v1.22 will include support required for that to work. Tests should be added before it is released.
https://github.com/go-gitea/gitea/pull/28965/files still being worked on (last activity this week). Progress is good.
It's been merged.
Time to cherry pick it into forgejo @earl-warren, to bring upload-artifact@v4 to a reality!
#156 should do it runner side.
It is in Forgejo as of last week.
Reminder to close this issue once it has been confirmed to work with the upcoming release of the runner 3.4.0, either because an automated test was added to end-to-end or because someone reports it working manually.
https://code.forgejo.org/forgejo/end-to-end/pulls/121/files verifies it works (tested locally and requires Forgejo 7.0+ and Forgejo runner 3.4+, will be in the CI from now on), with the caveat that it needs a forked version of the action that claims to not be GHES. These forked versions are advertised in the comment of the mirror at:
and they are made available at:
I made a note to check them in two months from now: the fork is likely to not be necessary once the protocol is supported by GHES which will happen eventually.
Fixed in https://code.forgejo.org/forgejo/runner/releases/tag/v3.4.0