Advance PG19 branch to Apache AGE version 1.8.0 (#2455)

[jrgemignani]

NOTE: This is a beta release of Apache AGE on PostgreSQL 19 (19beta1)

NOTE: Upgrade scripts are included. HOWEVER, this is a beta release and
you should backup everything before using them.

Updated the following files to advance the Apache AGE version to 1.8.0

modified: META.json
modified: README.md
modified: RELEASE
renamed: age--1.7.0--y.y.y.sql -> age--1.7.0--1.8.0.sql
modified: age.control
modified: docker/Dockerfile
new file: age--1.8.0--y.y.y.sql

Updated the following file to lock PG19 to require 1 other reviewer for merges:

modified: .asf.yaml

Resolved conflicts:
modified: docker/Dockerfile

Updated:
modified: META.json
modified: README.md
modified: RELEASE

[Copilot]

Pull request overview

Advances the PG19 branch to Apache AGE 1.8.0 (targeting PostgreSQL 19beta1), updating versioned metadata/docs and extension upgrade scaffolding to match the new release.

Changes:

• Bump reported AGE version to 1.8.0 across release notes, README badge, extension control, and PGXN metadata.
• Introduce/rename extension upgrade scripts for the 1.7.0 → 1.8.0 upgrade path and add the next-upgrade template.
• Update the Docker image to install the 1.8.0 SQL and base on postgres:19beta1.

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
RELEASE	Updates release notes for 1.8.0 / PG19beta1 and lists included changes.
README.md	Updates displayed release/version badges and supported PostgreSQL versions/docs links.
META.json	Bumps extension metadata version/file references for the 1.8.0 release.
docker/Dockerfile	Updates container build to PG19beta1 and copies the 1.8.0 extension SQL into the runtime image.
age.control	Sets default_version to 1.8.0.
age--1.7.0--1.8.0.sql	Renames/updates the upgrade script header for the 1.7.0 → 1.8.0 upgrade.
age--1.8.0--y.y.y.sql	Adds the next-upgrade template file for future version transitions.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 7 out of 7 changed files in this pull request and generated 4 comments.

[jrgemignani]

From Opus 4.8 Max 1M -

PR #2463 review — Advance PG19 branch to Apache AGE 1.8.0

Verdict: Complete and correct — LGTM to merge. It faithfully mirrors the master
1.8.0 advance (#2455) for the PG19 branch and additionally bundles the driver-image
fix. Built and tested against PostgreSQL 19beta1; two minor, non-blocking notes below.

Completeness — all version surfaces bumped

File	Change
age.control	default_version → 1.8.0
META.json	version → 1.8.0, file → age--1.8.0.sql, PostgreSQL → 19.0.0
README.md	badge v1.7.0→v1.8.0, PG18→PG19 doc links, supported list adds 19beta1
RELEASE	1.8.0 notes for the PG19 branch (PG19beta1) + BETA warning
age--1.7.0--y.y.y.sql → age--1.7.0--1.8.0.sql	renamed; template lines removed; echo → '1.8.0'
age--1.8.0--y.y.y.sql	new next-version template
docker/Dockerfile	COPY age--1.7.0.sql → age--1.8.0.sql
drivers/{docker-compose.yml, jdbc, nodejs}	dev_snapshot_master → dev_snapshot_PG19

Correctness — verified empirically on PG19beta1

• Clean COPT=-Werror build (0 warnings); Makefile generates age--1.8.0.sql, so
  CREATE EXTENSION resolves at the new default.
• Fresh install reports 1.8.0 and a cypher CREATE works.
• age_upgrade regression passes — All 43 tests passed (the authoritative 1.7.0→1.8.0
  check; it synthesizes the real 1.7.0 from git history and applies the upgrade).
• The age--1.7.0--1.8.0.sql DDL is byte-identical to master's already-validated script.

Non-blocking notes

1. (Pre-existing, not introduced here) The pg_upgrade support functions live in both
   the sql/ source (→ generated default install) and the age--1.7.0--1.8.0.sql upgrade
   script. This is safe for real upgrades (the 1.7.0 release predates those functions, so
   the upgrade script adds them cleanly — confirmed by age_upgrade). The only way to trip
   a "function ... already exists" error is if a stale, generated age--1.7.0.sql lingers
   in the extension dir and someone does CREATE EXTENSION age VERSION '1.7.0' then upgrades.
   A clean 1.8.0 build ships only age--1.8.0.sql + upgrade scripts, so packaged installs
   are unaffected. Worth tracking as a latent footgun; out of scope for this PR.
2. Cosmetic: age--1.8.0--y.y.y.sql carries a duplicated -- This will only work within a major version… comment (a stray block above the --* header). It's identical on
   master's template, so this PR correctly mirrors master — worth a one-line cleanup on both
   branches eventually, harmless as-is.

[gregfelice]

LGTM — approving.

Reviewed the full diff (8 files, no C code — a pure version/metadata advance for the PG19 branch). Every version surface is bumped consistently to 1.8.0 / PG19:

• age.control: default_version → 1.8.0
• META.json: version → 1.8.0, file → age--1.8.0.sql, PostgreSQL prereq → 19.0.0
• README.md: badge v1.8.0, PG18 → PG19 doc links, supported list adds 19beta1
• RELEASE: 1.8.0 notes + BETA-on-PG19beta1 warning
• docker/Dockerfile: COPY age--1.7.0.sql → age--1.8.0.sql (matches new default)
• .asf.yaml: adds PG19 branch protection (1 approving review)

Independently verified the one file with executable content: diffed age--1.7.0--1.8.0.sql against master's #2455 upgrade script — byte-identical (1120 lines). The rename only strips the --* template scaffolding and sets the \echo target to '1.8.0'. CI green across all build jobs, mergeStateStatus CLEAN.

Nit (non-blocking, mirrors master): the new age--1.8.0--y.y.y.sql template carries a duplicated -- This will only work within a major version... comment block — worth a one-line cleanup on both branches eventually, harmless as-is.