github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-07-10 16:44:50 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Better solution to actions/upload-artifact v4 #15038

New Issue
Open
opened 2025-11-02 11:28:43 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-02 11:28:43 -06:00
Owner
Copy Link

Originally created by @TheBrokenRail on GitHub (Oct 20, 2025).

Feature Description

Right now, this is the situation:

  • Gitea supports actions/upload-artifact (and actions/download-artifact) v4
  • GitHub has officially deprecated actions/upload-artifact v3
  • GitHub Enterprise Server (GHES) still does not support actions/upload-artifact v4
    • And as far as I can tell, they have been completely radio-silent about when this will be fixed (which is kind of horrifying)
  • actions/upload-artifact v4 things Gitea is GHES and automatically blocks it

There are two workarounds:

  1. Keep using actions/upload-artifact v3
    • For obvious reasons, I'd prefer not to rely on deprecated code
    • And I imagine the Gitea maintainers don't want to support both the v3 and v4 APIs
  2. Use a patched version of actions/upload-artifact v4 (like this)
    • This works (and is arguably the best solution)
    • But it relies on one person's (really outdated) fork of actions/upload-artifact v4
    • I could make my own soft-fork, but then that's another thing I'd have to maintain

I wonder if it would be possible to have Gitea automatically patch actions/upload-artifact or somehow trick it into thinking it's running on github.com?

Screenshots

No response

Originally created by @TheBrokenRail on GitHub (Oct 20, 2025). ### Feature Description Right now, this is the situation: - Gitea supports `actions/upload-artifact` (and `actions/download-artifact`) v4 - GitHub has officially deprecated `actions/upload-artifact` v3 - GitHub Enterprise Server (GHES) *still* does not support `actions/upload-artifact` v4 - And as far as I can tell, they have been completely radio-silent about when this will be fixed (which is kind of horrifying) - `actions/upload-artifact` v4 things Gitea is GHES and automatically blocks it There are two workarounds: 1. Keep using `actions/upload-artifact` v3 - For obvious reasons, I'd prefer not to rely on deprecated code - And I imagine the Gitea maintainers don't want to support both the v3 and v4 APIs 2. Use a patched version of `actions/upload-artifact` v4 (like [this](https://github.com/christopherhx/gitea-upload-artifact)) - This works (and is arguably the best solution) - But it relies on one person's (really outdated) fork of `actions/upload-artifact` v4 - I could make my own soft-fork, but then that's another thing I'd have to maintain I wonder if it would be possible to have Gitea automatically patch `actions/upload-artifact` or somehow trick it into thinking it's running on `github.com`? ### Screenshots _No response_
GiteaMirror added the topic/gitea-actionstype/proposal labels 2025-11-02 11:28:43 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label topic/gitea-actions type/proposal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#15038
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?