ci.yml's pg-tle-test job env var is named PG_TLE_BUILD_VERSION instead of the more natural PGTLE_VERSION, worked around because pgxntool's own Makefile variable of the same name (pgtle:'s $(if $(PGTLE_VERSION),--pgtle-version $(PGTLE_VERSION))) gets silently auto-imported from the environment by Make, causing make run-pgtle to generate into the wrong pg_tle/ directory instead of the correct range directory. Filed upstream as Postgres-Extensions/pgxntool#78.
Once #78 lands (whether by renaming pgxntool's internal variable to something collision-resistant, or some other fix) and is synced into this repo's vendored pgxntool copy, rename PG_TLE_BUILD_VERSION back to PGTLE_VERSION in .github/workflows/ci.yml and drop the explanatory comment describing the collision.
ci.yml's pg-tle-test job env var is named PG_TLE_BUILD_VERSION instead of the more natural PGTLE_VERSION, worked around because pgxntool's own Makefile variable of the same name (pgtle:'s$(if $ (PGTLE_VERSION),--pgtle-version $(PGTLE_VERSION))) gets silently auto-imported from the environment by Make, causing make run-pgtle to generate into the wrong pg_tle/ directory instead of the correct range directory. Filed upstream as Postgres-Extensions/pgxntool#78.
Once #78 lands (whether by renaming pgxntool's internal variable to something collision-resistant, or some other fix) and is synced into this repo's vendored pgxntool copy, rename PG_TLE_BUILD_VERSION back to PGTLE_VERSION in .github/workflows/ci.yml and drop the explanatory comment describing the collision.