Attach the Arch package to GitHub releases - #2
Merged
Merged
Conversation
- The arch CI job uploads its package as the arch-package artifact. Tag pushes (and arch_release dispatches) build PKGBUILD unmodified from its release tag and fail if pkgver does not match the tag. - release:draft attaches the Arch package and writes one SHA256SUMS for the .deb, .rpm and Arch package. - npm run check fails if PKGBUILD pkgver differs from package.json. - Document pacman installation of the release asset. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Summary
archCI job uploads the built package as anarch-packageartifact. Tag pushes, andworkflow_dispatchruns witharch_release, buildpackaging/aur/PKGBUILDunmodified from its release tag, exactly what AUR users will get. They fail ifpkgverdoes not match the tag. Other pushes still build the pushed commit.release:draftattachescommand-center-<version>-<pkgrel>-x86_64.pkg.tar.zstand writes oneSHA256SUMScovering all three packages.npm run checknow fails if the PKGBUILDpkgverdrifts frompackage.json.pacman -U.AUR account registration is currently closed, so this gives Arch/Garuda users a prebuilt package in the meantime.
After merge
Run the workflow on
mainwitharch_releaseto build v0.6.0 from its tag, then attach the package to the published v0.6.0 release with a regeneratedSHA256SUMS.🤖 Generated with Claude Code