Skip to content

Release 0.5.0 - #48

Merged
jnasbyupgrade merged 1 commit into
Postgres-Extensions:masterfrom
jnasbyupgrade:release-0.6.0
Oct 8, 2026
Merged

jnasbyupgrade merged 1 commit into
Postgres-Extensions:masterfrom
jnasbyupgrade:release-0.6.0

Conversation

@jnasbyupgrade

@jnasbyupgrade jnasbyupgrade commented Oct 8, 2026 •

Copy link
Copy Markdown
Collaborator

Release distribution 0.5.0: test_factory 0.5.0, test_factory_pgtap 0.1.0.

0.5.0 was the in-development version (bumped in 2017, never released or published to PGXN, whose latest is 0.4.2), so this releases it with everything since rather than skipping to a new number.

  • test_factory: default_version → 0.5.0; sql/test_factory--0.5.0.sql regenerated from current source; the 0.5.0 → stable update script is dropped, since there's nothing to update from.
  • test_factory_pgtap: its --stable update script is a genuine no-op, so default_version goes back to 0.1.0 and the script stays un-renamed (excluded from the archive by .gitattributes).
  • META.in.json already says 0.5.0, so it's unchanged.
  • Add HISTORY.asc (this repo had no changelog yet).

No ALTER EXTENSION update path reaches 0.5.0, from either 0.3.1 (what PGXN 0.4.2 installed) or a pre-release 0.5.0 installed from git. HISTORY.asc says to drop and recreate.

Pre-release checks

  • test_factory_pgtap--0.1.0.sql, which shipped in dist 0.4.2, was edited after release (Drop the original_role temp table from install (#12/#13) #20, Add sql-lint: style linter for PostgreSQL SQL files #24). The only change from the published file is how the install script saves and restores the caller's role; the objects it creates are identical.
  • make verify-results passes locally on PG17.
  • Built from a git archive of this commit: make && make install, then CREATE EXTENSION test_factory_pgtap CASCADE reports test_factory 0.5.0 / test_factory_pgtap 0.1.0.
  • No CI dependency-override toggle is set.

After merge

make tag PGXN_REMOTE=upstream && make dist PGXN_REMOTE=upstream, upload the zip to PGXN Manager, then a follow-up PR that returns both extensions to stable and re-seeds 0.5.0 → stable / 0.1.0 → stable update scripts.

(The branch is still named release-0.6.0 from the first draft; the content is 0.5.0.)

🤖 Generated with Claude Code

@coderabbitai

coderabbitai Bot commented Oct 8, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration
  • Configuration used: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: 8c755dd4-c9fa-42dd-87d6-ab641bec7ae1

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

0.5.0 was the in-development version and never reached PGXN, so release
it with everything since: test_factory 0.5.0 is regenerated from current
source and its 0.5.0 -> stable update script is dropped. test_factory_pgtap
stays at 0.1.0 (its stable update script is a no-op), so its
default_version reverts to 0.1.0. Add HISTORY.asc with the 0.5.0 changelog.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@jnasbyupgrade jnasbyupgrade changed the title Release 0.6.0 Release 0.5.0 Oct 8, 2026
@jnasbyupgrade
jnasbyupgrade merged commit 710d104 into Postgres-Extensions:master Oct 8, 2026
16 checks passed
@jnasbyupgrade
jnasbyupgrade deleted the release-0.6.0 branch October 8, 2026 19:34
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