Conversation
|
I've added |
There was a problem hiding this comment.
Pull request overview
This PR prepares the pg_stat_ch extension for distribution on PGXN (PostgreSQL Extension Network) by changing the extension schema version format from 0.1.0 to 0.1 while maintaining the release version at 0.1.7. The simplified version format allows binary-compatible minor releases without requiring version-specific SQL migration files for each patch release.
Changes:
- Renamed SQL installation file from
pg_stat_ch--0.1.0.sqltopg_stat_ch--0.1.sqlto match new version format - Added PGXN release infrastructure including META.json metadata, Makefile for PGXS compatibility, and automated release workflow
- Configured git export rules to exclude development files from distribution packages
Reviewed changes
Copilot reviewed 7 out of 9 changed files in this pull request and generated 13 comments.
Show a summary per file
| File | Description |
|---|---|
| sql/pg_stat_ch--0.1.sql | New SQL installation file with simplified version number (0.1 instead of 0.1.0) |
| cmake/GitVersion.cmake | Updated fallback version from "0.1.0" to "0.1" |
| benchmark/Dockerfile | Updated to reference new SQL filename pg_stat_ch--0.1.sql |
| Makefile | New PGXS-compatible Makefile for standard PostgreSQL extension builds and PGXN distribution |
| META.json | New PGXN metadata file describing extension, maintainers, dependencies, and resources |
| CLAUDE.md | Updated documentation to reflect new SQL filename |
| .gitignore | Added pattern to ignore release artifact zip files |
| .github/workflows/pgxn.yml | New workflow to automate PGXN releases on tagged commits |
| .gitattributes | New export rules to exclude development files from distribution archives |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 7 out of 9 changed files in this pull request and generated 4 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Change the extension version from `0.1.0` to `0.1`, but keep the release
version at `0.1.7`. This allows binary-compatible minor releases without
the need for version-specific SQL migration files.
Add a workflow to release on PGXN. Details:
* Add a simple `Makefile` so that typical PGXS-style tooling works. It
doesn't actually use PGXS except to determine the shared library
suffix. The `installcheck` is a to-do for now.
* Add `.gitattributes` to prevent files we don't want distributed from
being included in the release.
* Include submodules in the release, so that builds will work.
* Add `META.json` to describe the extension to PGXN.
1 participant
Change the extension version from
0.1.0to0.1, but keep the release version at0.1.7. This allows binary-compatible minor releases without the need for version-specific SQL migration files.Add a workflow to release on PGXN. Details:
Makefileso that typical PGXS-style tooling works. It doesn't actually use PGXS except to determine the shared library suffix. Theinstallcheckis a to-do for now..gitattributesto prevent files we don't want distributed from being included in the release.META.jsonto describe the extension to PGXN.