[jnasbyupgrade]

make pgtle PGXNTOOL_PGTLE_VERSION=<value> and pgtle.sh --pgtle-version <value> now fail unless <value> is exactly one of the pg_tle range names in pgtle.sh's PGTLE_VERSIONS: 1.0.0-1.4.0, 1.4.0-1.5.0 or 1.5.0+. Before this change, any value was used verbatim as the output directory, so a plain pg_tle version such as 1.5.0 silently created a bogus pg_tle/1.5.0/ directory with capability unknown.

$ make pgtle PGXNTOOL_PGTLE_VERSION=1.5.0
ERROR: invalid pg_tle version range: '1.5.0'
       Valid ranges: 1.0.0-1.4.0 1.4.0-1.5.0 1.5.0+
       '1.5.0' looks like a pg_tle version; did you mean 1.5.0+?

• The check is in pgtle.sh's --pgtle-version handling, so make pgtle and direct pgtle.sh calls both get it. The list of valid ranges comes from PGTLE_VERSIONS, not from a second hardcoded list.
• The "did you mean" range comes from the existing --get-dir logic, including its pre-release handling (1.5.0rc1 maps to 1.4.0-1.5.0). It is only shown when --get-dir accepts the value; latest, an empty value, and 1.5.1000 get only the list of valid ranges. --get-dir runs as a child process because get_version_dir depends on errexit to stop when parsing fails, and bash suspends errexit inside an if condition. Called in-process, latest came back as 1.5.0+. --get-dir's own behavior is unchanged.
• README.asc/README.html: the two sentences saying other values are passed through unvalidated now describe the error. HISTORY.asc has a STABLE entry.

Why validate instead of mapping a plain version to its range

• The output directory always equals the value given.
• No second accepted spelling needs documenting and testing.
• The error turns the common mistake into a one-step fix.
• It matches the README wording from Fix stale and inaccurate user docs #129: "must be one of those range names exactly; it is not mapped from a plain pg_tle version".

Merge order

This adds behavior, so merge this PR before the paired pgxntool-test PR (pgxntool-test CLAUDE.md, "Merge Order for Paired PRs"). Until this PR lands, the new tests fail against pgxntool master.

Related pgxntool-test PR: Postgres-Extensions/pgxntool-test#101

🤖 Generated with Claude Code

[coderabbitai]

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: 9d979910-6201-4e6e-b070-d8b5248afa22

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

• X
• Mastodon
• Reddit
• LinkedIn

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