v1.4.0 adds the GIT_BUNDLE_OPTS and ZIP_BUNDLE_OPTS environment variables. The former is passed to git archive and the latter to zip, and let additional options be passed to those commands. For example, the vectorize extension’s release workflow sets GIT_BUNDLE_OPTS: --add-file META.json because git archive archives only checked-in files, and META.json is not checked in but generated from META.json.in.

v1.4.1 fixes an issue where git archive was never actually used to build a release zip archive. This changed at some point without noticing due to the introduction of the safe.directory configuration in recent versions of Git. Inside the container the directory was never trusted, and the pgxn-bundle command caught the error, decided it wasn’t working with a Git repository, and used the zip command, instead.

As a result, a number of recent releases have included files they shouldn’t, such as the contents of the .git directory. The fix disables safe.directory so that the repository directory is always trusted inside the container, as needed in GitHub actions.

If you use pgxn-bundle in a GitHub workflow, be aware that recent releases (since November 2021 at least) include stuff that it should not, including the .git directory (here’s a list) and patterns excluded in .gitattributes. Your next release should be cleaner.

v1.4.1 also allows the setting of the PROFILE environment variable, so that the default PROFILE=--Werror can be overridden.

v1.4.2 adds (and v1.4.3 improves, see below) git-archive-all to the image, and the GIT_ARCHIVE_CMD environment variable to tell pgxn-bundle which archive command to use, either archive or archive-all. The latter is useful for repositories that use Git submodules and need to include their contents in the release, as demonstrated in this plv8 pull request.

v1.4.2 also adds cmake and the libarchive-tools package to the image. The latter bundles in libarchive tools like bsdtar and bsdcpio, which might be useful for editing Zip files in place.

v1.4.3 passes the --force-submodules option to git-archive-all, because otherwise submodules weren’t included in the bundle.

All of this should just start showing up in your GitHub workflows as long as they use container: pgxn/pgxn-tools or container: pgxn/pgxn-tools@v1.

Questions? Post em in the #extensions channel on the Postgres Slack or to the attention of the PGXN Mastodon bot.

I’m proud to tell you that a new version of pgxn_utils was released!

Now you can release a distribution to PGXN in five steps!

First, install it:

gem install pgxn_utils

Second, create your extension, optionally overwrite some defaults:

mkdir $HOME/extensions
cd $HOME/extensions
pgxn_utils skeleton my_extension --maintainer "Dickson S. Guedes"

Third, code!

Fourth, bundle it:

pgxn_utils bundle my_extension
Extension generated at: /home/guedes/extensions/my_extension-0.0.1.zip

Fifth, release it:

pgxn_utils release my_extension-0.0.1.zip
Enter your PGXN username: guedes
Enter your PGXN password: ******
Trying to release my_cool_extension-0.0.1.zip ... released successfully!
Visit: https://manager.pgxn.org/distributions/my_cool_extension/0.0.1

Ah, you can export PGXN_USER and PGXN_PASSWORD if you are tired to type your username and password every time.

Check this out!.