Add PGXN release workflow by theory · Pull Request #1711 · apache/age
Oooh, okay. Then you'd be best off with separate release names for each one. SO in 5bf40ed I set the name of the distribution to "name": "ApacheAGE16", and the Postgres version requirements to "PostgreSQL": ">= 16.0.0, < 17.0.0". See a sample build here, where instead of releasing it runs ls -lh and shows ApacheAGE16-1.5.0.zip.
This allows you to have separate distributions for 13, 14, 15, 16, by adjusting these two items to indicate the supported version. For 15, for example:
and
"PostgreSQL": ">= 15.0.0, < 16.0.0"
You would need to replicate this for each maintenance branch and release them separately.