Add release package workflow#190
Merged
Merged
Conversation
pinodeca
force-pushed
the
package-release-workflow
branch
3 times, most recently
from
aea6073 to
0b2bef2
Compare
pinodeca
force-pushed
the
package-release-workflow
branch
from
a7f8cbf to
b0c4359
Compare
There was a problem hiding this comment.
Pull request overview
Adds an automated packaging/release pipeline to publish Debian artifacts for tagged releases, along with helper scripts to build and validate the resulting .deb packages and documentation for installing from release assets.
Changes:
- Added a new GitHub Actions workflow to build/validate Debian packages and upload them (plus source archives) to GitHub Releases.
- Added Debian packaging and package-validation scripts to produce
.debartifacts fromcargo pgrx packageoutput and runmake installcheckagainst an installed package. - Updated pgspot allowlist and documented package installation in the README.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 5 comments.
Show a summary per file
| File | Description |
|---|---|
.github/workflows/package-release.yml |
New workflow to build, validate, archive, and upload release assets for tags/manual dispatch. |
scripts/package-deb.sh |
Builds a Debian package from the pgrx packaged usr/ tree and emits it into dist/. |
scripts/validate-deb-package.sh |
Installs the produced .deb into a clean Debian container, boots PostgreSQL, and runs make installcheck. |
scripts/run-pgspot.sh |
Allows pgspot PS017 finding for the ~> operator emitted by generated SQL. |
README.md |
Documents installing pg_durable from Debian packages and release source archives. |
tjgreen42
approved these changes
Jun 3, 2026
tjgreen42
left a comment
tjgreen42
left a comment
Contributor
There was a problem hiding this comment.
LGTM, just need to update the PR description as per the robot's advice
pinodeca
added a commit
that referenced
this pull request
Jun 10, 2026
- The build/validate matrix and README only target amd64, so the arm64 branches in the packaging scripts were dead code. Remove them so the scripts reject unsupported architectures explicitly. - Scope contents:write to the release job only; the rest of the workflow runs read-only (least privilege). - Upload the .deb files as release assets directly instead of wrapping them in zips, matching the README's documented asset names. - Publish a SHA256SUMS file so downloaders can verify assets.
This was referenced Jun 17, 2026
Closed
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.
Summary
.debpackages and source archives directly as release assets, plus aSHA256SUMSfileValidation
Note: unrelated untracked workspace files were left untouched.