Release workflow: fix git dubious-ownership failure in “Release artifacts and AUR”#2
Merged
Merged
Conversation
Copilot
AI
changed the title
[WIP] Fix failing GitHub Actions job Release artifacts and AUR
Release workflow: fix git dubious-ownership failure in “Release artifacts and AUR”
Jun 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The release pipeline was failing in the Release artifacts and AUR job when
make checksumsinvokedgit archiveinside the Arch container. Git rejected the workspace as an unsafe repository (detected dubious ownership), stopping artifact generation and downstream AUR steps.Root cause
safe.directoryconfiguration before running git-based packaging commands (dist/checksums).Workflow change
.github/workflows/release.ymlto mark the Actions workspace as safe for git operations in this job.git archiveand other git commands used during release artifact creation run consistently under the container’s ownership model.Scope