Releases

Release tagging convention

Starting with release 0.24.dev0+limno.1, we established a tag based on the pygeoapi version and an incremented limno.# tag relative to the pygeoapi version. e.g. 0.23.3+limno.2 0.24.1+limno.1 0.23.3+limno.1

The previous convention (now deprecated) had been to tag based on the pygeoapi version and an incremented limno.# tag. e.g. 0.23.dev+limno.13. The old convention provides information relative to other releases, rather than releases relative to the same base version, which sort of breaks from semantic versioning intent. This pattern also broke for scenario where we are maintaining parallel versions (i.e. 0.23.x) for compatibility, while also working on a different version (i.e. 0.24.x) for testing and new feature development. In this case we would be mixing and matching limno.# tags to keep with the convention.

0.23.3+limno.17 0.24.1+limno.16 0.23.3+limno.15