generated from actions/typescript-action
-
Notifications
You must be signed in to change notification settings - Fork 219
Open
Labels
help wantedExtra attention is neededExtra attention is neededtype: bugSomething isn't workingSomething isn't working
Description
I know the gitea support is still experimental so I thought some feedback would be nice :)
I still haven't managed to get it to work, it always fails with "Bad credentials":
[... build works fine ...]
Looking for artifacts in:
/workspace/OWNER/REPO/target/release/bundle/deb/APPNAME_0.1.2-beta1_amd64.deb
/workspace/OWNER/REPO/target/release/bundle/deb/APPNAME_0.1.2-beta1_amd64.deb.sig
/workspace/OWNER/REPO/target/release/bundle/rpm/APPNAME-0.1.2-beta1-1.x86_64.rpm
/workspace/OWNER/REPO/target/release/bundle/rpm/APPNAME-0.1.2-beta1-1.x86_64.rpm.sig
/workspace/OWNER/REPO/target/release/bundle/appimage/APPNAME_0.1.2-beta1_amd64.AppImage
/workspace/OWNER/REPO/target/release/bundle/appimage/APPNAME_0.1.2-beta1_amd64.AppImage.sig
/workspace/OWNER/REPO/target/release/bundle/appimage/APPNAME_0.1.2-beta1_amd64.AppImage.tar.gz
/workspace/OWNER/REPO/target/release/bundle/appimage/APPNAME_0.1.2-beta1_amd64.AppImage.tar.gz.sig
Found artifacts:
/workspace/OWNER/REPO/target/release/bundle/deb/APPNAME_0.1.2-beta1_amd64.deb
Couldn't find release with tag 0.1.2-beta1. Creating one.
Uploading APPNAME_0.1.2-beta1_amd64.deb...
::error::Bad credentials - https://docs.github.com/rest
❌ Failure - Main tauri-apps/tauri-action@v0.6.1
::set-output:: releaseHtmlUrl=https://GITEA_SERVER/OWNER/REPO/releases/tag/0.1.2-beta1
Workflow config:
- uses: tauri-apps/tauri-action@v0.6.1
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
with:
githubBaseUrl: https://GITEA_SERVER/api/v1
isGitea: true
tagName: "__VERSION__"
releaseName: "APPNAME __VERSION__"
releaseBody: ":rocket:"
It manages to create the release and tag it (or see that there's an existing one) so the api stuff seems to work, just the uploadReleaseAsset part fails. So I think it's not a permission issue (then creating the release would also fail). I also tested it with a token with all permissions, didn't change a thing.
One interesting thing that I've noticed is that there is no API request (POST) for the upload, the gitea server log only has these entries:
2026/02/06 18:21:02 HTTPRequest [I] router: completed GET /api/v1/repos/OWNER/REPO/releases/tags/0.1.2-beta1 for RUNNER_IP:36084, 404 Not Found in 21.9ms @ repo/release_tags.go:17(repo.GetReleaseByTag)
2026/02/06 18:21:03 HTTPRequest [I] router: completed POST /api/v1/repos/OWNER/REPO/releases for RUNNER_IP:36084, 201 Created in 130.8ms @ repo/release.go:189(repo.CreateRelease)
2026/02/06 18:21:03 HTTPRequest [I] router: completed GET /api/v1/repos/OWNER/REPO/releases/102486/assets?per_page=100 for RUNNER_IP:36182, 200 OK in 33.4ms @ repo/release_attachment.go:101(repo.ListReleaseAttachments)
Seems like the error happens before the request is made.
Maybe this will help to improve gitea support :)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
help wantedExtra attention is neededExtra attention is neededtype: bugSomething isn't workingSomething isn't working