From 638084bb8ba4cefb35604d50a8eaa96979e90e1c Mon Sep 17 00:00:00 2001
From: pgclone contributor <claude@local>
Date: Wed, 13 May 2026 22:13:11 +0000
Subject: [PATCH] chore: sync v4.3.2 metadata in META.json and README badge
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Trailing miss from the v4.3.2 release: the PGXN extension metadata
file META.json and the README shields.io version badge were both
still on 4.3.0, dating back to the pre-v4.3.1 work. The control
file, C version string, SQL files, and all docs were correctly
bumped; only these two surfaces lagged.

Files updated:
  META.json
    - top-level "version": 4.3.0 -> 4.3.2
    - provides.pgclone.file:    "sql/pgclone--4.3.0.sql" -> 4.3.2
    - provides.pgclone.version: 4.3.0 -> 4.3.2
  README.md
    - shields.io badge URL + linked release tag: v4.3.0 -> v4.3.2

The v4.3.2 source tarball at github.com/.../archive/refs/tags/
v4.3.2.tar.gz currently contains the stale META.json, which would
mislead any PGXN tooling consuming this release. The v4.3.2 tag
will be moved to include this fix as a separate post-merge step.

Remaining v4.3.0 / v4.3.1 strings in src/pgclone.c, SECURITY.md,
and the README roadmap are historical references ("As of v4.3.1,
pgclone re-parses every source conninfo…", "v4.3.0: Consistent-
snapshot clones…") and are intentionally preserved — they document
when features shipped, not the current version.

No code change. No SQL change. No CI behaviour change.
---
 META.json | 6 +++---
 README.md | 2 +-
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/META.json b/META.json
index 82c68ea..827d1b8 100644
--- a/META.json
+++ b/META.json
@@ -2,14 +2,14 @@
    "name": "pgclone",
    "abstract": "Clone PostgreSQL databases, schemas, tables between staging, test, dev and prod environments",
    "description": "PostgreSQL extension for easily cloning your DB, Schemas, Tables and more between environments",
-   "version": "4.3.0",
+   "version": "4.3.2",
    "maintainer": "Valeh Agayev <valeh.agayev@gmail.com>",
    "license": "postgresql",
    "provides": {
       "pgclone": {
          "abstract": "Clone PostgreSQL databases, schemas, and tables across environments",
-         "file": "sql/pgclone--4.3.0.sql",
-         "version": "4.3.0"
+         "file": "sql/pgclone--4.3.2.sql",
+         "version": "4.3.2"
       }
    },
    "prereqs": {
diff --git a/README.md b/README.md
index 7d3e5a0..963f13a 100644
--- a/README.md
+++ b/README.md
@@ -3,7 +3,7 @@
 [![CI](https://github.com/valehdba/pgclone/actions/workflows/ci.yml/badge.svg)](https://github.com/valehdba/pgclone/actions/workflows/ci.yml)
 [![Postgres 14–18](https://img.shields.io/badge/Postgres-14%E2%80%9318-336791?logo=postgresql&logoColor=white)](https://github.com/valehdba/pgclone)
 [![License](https://img.shields.io/badge/License-PostgreSQL-blue.svg)](https://github.com/valehdba/pgclone/blob/main/LICENSE)
-[![Version](https://img.shields.io/badge/version-4.3.0-orange)](https://github.com/valehdba/pgclone/releases/tag/v4.3.0)
+[![Version](https://img.shields.io/badge/version-4.3.2-orange)](https://github.com/valehdba/pgclone/releases/tag/v4.3.2)
 
 A PostgreSQL extension that clones databases, schemas, tables, and functions between PostgreSQL instances — directly from SQL. No `pg_dump`, no `pg_restore`, no shell scripts.