Update version numbers, v1.1.0 #13
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gadomski
approved these changes
Jun 5, 2025
| - **STAC API - Item Search** binding: <https://api.stacspec.org/v1.0.0/item-search#sort> | ||
| - **STAC API - Features** binding: <https://api.stacspec.org/v1.0.0/ogcapi-features#sort> | ||
| - **STAC API - Collection Search** binding: <https://api.stacspec.org/v1.0.0-rc.1/collection-search#sort> | ||
| - **STAC API - Item Search** binding: <https://api.stacspec.org/v1.1.0/item-search#sort> |
There was a problem hiding this comment.
😬 I think I understand what's going on here, but it feels so strange to have a https://api.stacspec.org/v1.1.0/item-search when item search itself is still v1.0.0.
There was a problem hiding this comment.
Yeah, how do we handle this? I think it is correct as it is, just weird that we have extensions of extensions with differing version numbers.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed Changes:
Note: There's some weirdness goind on with the version numbers, e.g. for collection-search the version numbers came from the collection search extension, while now I've updated them to follow the versioning of the sort extension, jumping from 1.0.0-rc.1 to 1.1.0 (without a 1.0.0). Similarly, sortables use the version number of OGC API Features right now.
PR Checklist: