Skip to content

Link the PGXN distribution from README and INSTALL - #10

Merged
jdatcmd merged 1 commit into
masterfrom
docs/pgxn-link
Aug 26, 2026
Merged

Link the PGXN distribution from README and INSTALL#10
jdatcmd merged 1 commit into
masterfrom
docs/pgxn-link

Conversation

@jdatcmd

@jdatcmd jdatcmd commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

plruby 2.5.0 is now published on PGXN: https://pgxn.org/dist/plruby/

README

  • PGXN badge alongside CI / PostgreSQL / Ruby / tests / license
  • pgxn install plruby as the first installation path, with the checkout build
    kept as the alternative, plus a note that either way builds from source and
    CREATE EXTENSION needs a superuser
  • the distribution page added to the documentation list

INSTALL

  • the same pgxn install plruby path in step 2, and the client's
    pgxn load -d mydb plruby next to CREATE EXTENSION in step 3
  • step 5 notes that pgxn install builds only the top-level extension, so a
    transform still needs its subdirectory built from pgxn download plruby or a
    checkout
  • the maintainer section records where to upload, that pgxn.org and
    api.pgxn.org trail master.pgxn.org until the next mirror sync (a 404 right
    after a release is expected, not a failed upload), and adds the README badge
    version to the list of things to bump when cutting a release

Docs only, no code or build changes. Every added link verified to return 200.

🤖 Generated with Claude Code

plruby 2.5.0 is published on PGXN, so point people at it: a badge next to
the others, "pgxn install plruby" as the first installation path, and the
distribution page in the documentation list. INSTALL gets the client's
"pgxn load -d mydb plruby" next to CREATE EXTENSION, and a note that
"pgxn install" builds only the top-level extension, so a transform still
needs its subdirectory built from a download or a checkout.

The maintainer section records where to upload and that pgxn.org and
api.pgxn.org trail master.pgxn.org until the next mirror sync, since a 404
right after a release reads as a failed upload otherwise. The README badge
version joins the list of things to bump when cutting a release.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@jdatcmd
jdatcmd merged commit 9c33e47 into master Aug 26, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant