<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/build-test-and-release-extensions-with-the-new-pgxn-github-actions-xzemlaooq" -->

---
title: Build, Test and Release Extensions with the New PGXN...
description: PGXN now offers three new GitHub Actions to replace the Docker-based pgxn-tools for building, testing and releasing Postgres extensions. The actions are...
canonical: https://daily.dev/posts/build-test-and-release-extensions-with-the-new-pgxn-github-actions-xzemlaooq
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Build, Test and Release Extensions with the New PGXN GitHub Actions | daily.dev
og:description: PGXN now offers three new GitHub Actions to replace the Docker-based pgxn-tools for building, testing and releasing Postgres extensions. The actions are...
og:url: https://daily.dev/posts/build-test-and-release-extensions-with-the-new-pgxn-github-actions-xzemlaooq
og:image: https://api.daily.dev/og/posts/xzEmlaOOq.png
og:image:alt: Build, Test and Release Extensions with the New PGXN GitHub Actions
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Build, Test and Release Extensions with the New PGXN GitHub Actions

**[Planet PostgreSQL](https://daily.dev/sources/planet-postgresql)** · 5 min read · 0 upvotes · 0 comments

## Summary

PGXN now offers three new GitHub Actions to replace the Docker-based pgxn-tools for building, testing and releasing Postgres extensions. The actions are pgxn/postgres-action to start a specific Postgres version, pgxn/matrix-action to generate a test matrix across Postgres versions, and pgxn/release-action to publish an extension on PGXN. They support all GitHub runner OSes and architectures and run faster than the old Docker approach. The matrix action updates its version list daily, so new Postgres betas get tested within a day. Windows support is still incomplete, especially for C extensions, and a pgrx-specific action is planned.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://postgr.es/p/9C7>

## Questions this post answers

### How do I release a PostgreSQL extension to PGXN using GitHub Actions?

Use the pgxn/release-action GitHub Action, checking out the repo and passing PGXN username and password secrets, with a dry-run flag tied to whether the push is a version tag starting with 'v'. The action runs 'git archive' to build a PGXN bundle and publish it, and it outputs an 'archive' value you can feed into a GitHub release step, for example with softprops/action-gh-release.

_Automating PostgreSQL extension releases gets easier to track with workflow guides like this on daily.dev._

### How can I test a PostgreSQL extension against multiple Postgres versions in CI without Docker?

Use pgxn/matrix-action to generate a test matrix of Postgres versions and pgxn/postgres-action to start a specific local Postgres server on the runner, replacing the Docker-based pgxn-tools approach. The matrix action's version list updates daily, so a new Postgres beta gets included in testing within a day unless a max-version is set. Options also let you set a minimum version, like 9.0, include beta or deprecated releases, and exclude platforms like Windows.

_Developers maintaining Postgres extension CI pipelines can follow matrix-testing approaches like this on daily.dev._

### How do I start Postgres in a GitHub Actions workflow with a custom shared_preload_libraries setting before building an extension?

Run pgxn/postgres-action first with 'no-start: true' to install Postgres without starting it, build and install the extension with make, then run pgxn/postgres-action again with the 'config' input set to 'shared_preload_libraries = my_module' to start Postgres with the module loaded, before running 'make installcheck'.

_Configuring preload libraries correctly in CI is easier to get right with workflow examples surfaced on daily.dev._

## Similar posts on daily.dev

- [PGXN Blog: From the Department of It's About Time:...](https://daily.dev/posts/pgxn-blog-from-the-department-of-it-s-about-time--vr2koubiy) · Planet PostgreSQL · 0 upvotes · 0 comments
- [GitHub - pgcentralfoundation/pgrx: Build Postgres Extensions with Rust\!](https://daily.dev/posts/github---pgcentralfoundation-pgrx-build-postgres-extensions-with-rust--gzoihklhh) · Hacker News · 0 upvotes · 0 comments
- [PGX announces support for EOL versions of PostgreSQL](https://daily.dev/posts/pgx-announces-support-for-eol-versions-of-postgresql-vjmcpsms7) · PostgreSQL · 0 upvotes · 0 comments
- [pgAdmin 4 v9.11 Released](https://daily.dev/posts/pgadmin-4-v9-11-released-hxlngyhcc) · PostgreSQL · 1 upvotes · 0 comments

---

Tags: [#testing](https://daily.dev/tags/testing), [#cicd](https://daily.dev/tags/cicd), [#postgresql](https://daily.dev/tags/postgresql), [#github-actions](https://daily.dev/tags/github-actions)

[View this post on daily.dev](https://daily.dev/posts/build-test-and-release-extensions-with-the-new-pgxn-github-actions-xzemlaooq)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Build, Test and Release Extensions with the New PGXN GitHub Actions","url":"https://daily.dev/posts/build-test-and-release-extensions-with-the-new-pgxn-github-actions-xzemlaooq","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/build-test-and-release-extensions-with-the-new-pgxn-github-actions-xzemlaooq"},"datePublished":"2026-11-16T20:46:06.954Z","dateModified":"2026-11-16T20:55:38.932Z","description":"PGXN now offers three new GitHub Actions to replace the Docker-based pgxn-tools for building, testing and releasing Postgres extensions. The actions are...","image":"https://media.daily.dev/image/upload/s--1KxV4ohY--/f_auto/v1722860400/public/Placeholder%2007","thumbnailUrl":"https://media.daily.dev/image/upload/s--1KxV4ohY--/f_auto/v1722860400/public/Placeholder%2007","isAccessibleForFree":true,"articleSection":"Planet PostgreSQL","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Planet PostgreSQL","logo":"https://media.daily.dev/image/upload/logos/placeholder.jpg","url":"https://daily.dev/sources/planet-postgresql"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/build-test-and-release-extensions-with-the-new-pgxn-github-actions-xzemlaooq","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"testing,cicd,postgresql,github-actions","timeRequired":"PT5M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Planet PostgreSQL","item":"https://daily.dev/sources/planet-postgresql"},{"@type":"ListItem","position":3,"name":"Build, Test and Release Extensions with the New PGXN GitHub Actions"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/build-test-and-release-extensions-with-the-new-pgxn-github-actions-xzemlaooq#faq","mainEntity":[{"@type":"Question","name":"How do I release a PostgreSQL extension to PGXN using GitHub Actions?","acceptedAnswer":{"@type":"Answer","text":"Use the pgxn/release-action GitHub Action, checking out the repo and passing PGXN username and password secrets, with a dry-run flag tied to whether the push is a version tag starting with 'v'. The action runs 'git archive' to build a PGXN bundle and publish it, and it outputs an 'archive' value you can feed into a GitHub release step, for example with softprops/action-gh-release. Automating PostgreSQL extension releases gets easier to track with workflow guides like this on daily.dev."}},{"@type":"Question","name":"How can I test a PostgreSQL extension against multiple Postgres versions in CI without Docker?","acceptedAnswer":{"@type":"Answer","text":"Use pgxn/matrix-action to generate a test matrix of Postgres versions and pgxn/postgres-action to start a specific local Postgres server on the runner, replacing the Docker-based pgxn-tools approach. The matrix action's version list updates daily, so a new Postgres beta gets included in testing within a day unless a max-version is set. Options also let you set a minimum version, like 9.0, include beta or deprecated releases, and exclude platforms like Windows. Developers maintaining Postgres extension CI pipelines can follow matrix-testing approaches like this on daily.dev."}},{"@type":"Question","name":"How do I start Postgres in a GitHub Actions workflow with a custom shared_preload_libraries setting before building an extension?","acceptedAnswer":{"@type":"Answer","text":"Run pgxn/postgres-action first with 'no-start: true' to install Postgres without starting it, build and install the extension with make, then run pgxn/postgres-action again with the 'config' input set to 'shared_preload_libraries = my_module' to start Postgres with the module loaded, before running 'make installcheck'. Configuring preload libraries correctly in CI is easier to get right with workflow examples surfaced on daily.dev."}}]}
```

