Add the loopwire-git AUR channel - #32
Merged
Merged
Conversation
Add loopwire-git as a third package base that follows the protected default branch and derives a monotonic version from Git history. Keep its moving-source build in a keyless verification lane; the AUR-key publisher only pushes reviewed metadata after that independent proof. Constraint: VCS packages must use a -git suffix and cannot execute moving source with publication credentials present Rejected: Fold rolling behavior into loopwire | would make the stable package non-reproducible and mislabel its update contract Confidence: high Scope-risk: moderate Reversibility: clean Directive: Keep loopwire, loopwire-bin, and loopwire-git as isolated package bases with one canonical default branch Tested: Full makepkg build at 0.1.0.r8.g007e47e, namcap, worktree publication preflight, AUR metadata smoke, requirements, docs, scripts, workflows, typecheck, tests, build Not-tested: Installation into a fresh Arch VM; workflow publication without a configured automation key Related: #29
dskvr
force-pushed
the
feature/29-loopwire-git
branch
from
September 4, 2026 13:29
677ab30 to
f107186
Compare
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
1 participant
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.
Closes #29.
Summary
loopwire-gitAUR recipe for the protected default branchloopwireand prebuiltloopwire-binas independent package basesSecurity boundary
The moving-source build runs in the keyless verification lane. The AUR-key publisher never executes VCS source; it validates and pushes reviewed
PKGBUILD,.SRCINFO, andLICENSE-MITmetadata only. Default-branch identity is passed and validated end-to-end, including the PKGBUILD#branch=selector.Live AUR evidence
loopwire-git0.1.0.r8.g007e47e-1e9ad7fbe8d2f3c2d6a9885125849daf7bda4d1f2Validation
makepkgbuild ofloopwire-git 0.1.0.r8.g007e47e-1namcapwarnings only; no errorspnpm verify:aurpnpm verify:requirementspnpm verify:docspnpm verify:scriptspnpm verify:workflowspnpm typecheckpnpm test— core 81, audio-host 123, desktop 91 passedpnpm buildpnpm verify:siteKnown gap
The package was built but not installed into a fresh Arch VM. Automated AUR publication still requires a dedicated passphrase-free key in the protected
aurGitHub environment; local publication used the existing interactive AUR key.