Releases: interuss/uas_standards
v3.3.0
v3.2.2
Fix repository_url specification (#18)
v3.2.0
Includes f3548v21 OpenAPI changes from:
Most notable change is the addition of optional fields enabling USSs to request an operational intent OVN.
What's Changed
- [CI] Fix MacOS builds: pin v13 image by @mickmis in #17
- [f3548v21] Target interuss/astm-utm-protocol repo as submodule and regen apis files by @mickmis in #16
Full Changelog: v3.1.0...v3.2.0
Contributors
Assets 2
v3.1.0
InterUSS flight_planning and RID observation APIs each progress by a minor version.
v3.0.0
Most of the InterUSS automated testing APIs are updated, including the addition of a versioning API. There are breaking changes to the newer flight_planning API. In addition, a number of constants (including scopes) are manually added to a number of APIs.
v2.1.0
Adds scope constants and updates to latest API versions.
v2.0.0
Incorporates new InterUSS automated testing interfaces for geospatial map queries and flight planning.
These API changes are not backwards-compatible:
- Previously, the
scdInterUSS automated testing interface was written to theflight_planningmodule; now it is written to thescdmodule - Inline types (data types described just for a single particular field inside an object) are now rendered with names in PascalCase rather than a MixOfPascal_and_snake_case.
v1.3.0
Incorporates changes to InterUSS automated testing interface for remote ID data injection (#8).
This API change is very slightly not backwards-compatible in RIDAuthData where the format field changes from a string to an int, but this data field is not in actual use currently as far as we are aware. Therefore, this change can be considered basically backwards-compatible. See automated_testing_interfaces pull request for more information.
v1.2.0
API data types
Adds data types for use with standard APIs:
- ASTM
- F3411-19
- F3411-22a
- ASTM F3548-21
- InterUSS automated testing
- RID injection
- RID observation
- Flight planning
- Geo-awareness