Releases: MobilityData/gbfs-json-schema
v4.0.0
It's been a long time since our last release!
This version consolidates all the updates and fixes made since Aug 2022.
(Reminder: the GitHub release version v4.0.0 is not the same as the GBFS specification version.)
What's Changed
- Typo fix in geofencing_zones.json by @pietercolpaert in #78
- V3.0-RC Schemas by @josee-sabourin in #79
- Fix invalid json, no trailing commas by @testower in #83
- FIX: replaces name field with localized string by @cmonagle in #82
- Fix schemas for v3.0-RC by @tdelmas in #85
- Add v3.0 to v3.0-RC schemas by @josee-sabourin in #88
- Refer to later versions in gbfs_versions.json by @josee-sabourin in #87
- fix: incorrect spec for "languages" property in system_information.json by @testower in #90
- Patch manifest.json by @josee-sabourin in #91
- Replace
requiredwith boolean (invalid) to array by @PierrickP in #92 - Remove
minItemsforvehicle_types_availableby @richfab in #94 - Updates
available_untilregex to allow timezones by @richfab in #97 - Fix description of station_information endpoint by @richfab in #98
- Add 3.0-RC2 schemas by @tdelmas in #100
- Validate uniqueness of values in Arrays of IDs by @richfab in #102
- Update schema id URL from NABSA to MobilityData repo by @richfab in #103
- Revert "Validate uniqueness of values in Arrays of IDs" by @richfab in #104
- Update JSON Schemas to v3.0 by @richfab in #105
- Feat/106 typescript language bindings by @Alessandro100 in #107
- Feat/publish gbfs language binding workflow by @Alessandro100 in #108
- Feat/109 java language bindings by @Alessandro100 in #110
- typescript license fix by @Alessandro100 in #111
- Feat/java language bindings cicd by @Alessandro100 in #112
- java license to Apache 2.0 by @Alessandro100 in #115
- Feat/116 java model name change by @Alessandro100 in #117
- fix/java script update by @Alessandro100 in #118
- Support v3.1-RC by @richfab in #120
- docs: updated link by @dersvenhesse in #124
- Add dependency reservation_price fields mutually exclusive by @richfab in #125
- Feat/113 go language bindings by @Alessandro100 in #119
- updated golang readme by @Alessandro100 in #127
- Point implementing class to overridden class by @testower in #129
- Feat/126 rust language bindings by @Alessandro100 in #128
- Feat/rust cicd by @Alessandro100 in #131
- Feat/typescript v31 rc by @Alessandro100 in #130
- typescript-package-script by @Alessandro100 in #132
- Fix/typescript include gen files by @Alessandro100 in #133
- update typescript publish with new token by @Alessandro100 in #134
- Add maximum value of 1 for current_fuel_percent by @richfab in #142
- feat: add openapi specification (to discuss !136) by @dersvenhesse in #138
- Added openAPI for 3.0 by @jcpitre in #145
- Update list of tz database time zones by @richfab in #147
- feat: update typescript package by @Alessandro100 in #152
- fix: ability to manually trigger typescript publish by @Alessandro100 in #154
- Feat: java package timezone update by @Alessandro100 in #153
- java deploy update sonatype token by @Alessandro100 in #155
- feat: update go v3.0 to new timezones by @Alessandro100 in #156
- Add 2.3 typescript models by @uwinkelvos in #157
- Add v2.3 support to TypeScript model README by @richfab in #159
- fix eco_labels required properties by @uwinkelvos in #160
- Add validation for presence of required files in discovery file by @testower in #163
- Remove workflow which adds issue to project by @richfab in #169
- version 3.1-RC2 release by @Alessandro100 in #166
- Replace
dependentRequiredkeywords bydependenciesby @richfab in #141 - Fix free_bike_status last_reported data type by @richfab in #171
- Replaces 'last_updated' values in test fixtures to conform to schema by @DanielKerger in #172
- Remove v3.1-RC JSON Schema (replaced by v3.1-RC2) by @richfab in #170
- feat: add v3.1-rc2 golang models and test by @davidgamez in #173
- Update dependencies in Cargo.toml by @FinnHuelsbusch in #168
- fix: cargo lock version 0.1.3 by @davidgamez in #178
- fix: rust cargo categories by @davidgamez in #179
New Contributors
- @pietercolpaert made their first contribution in #78
- @cmonagle made their first contribution in #82
- @PierrickP made their first contribution in #92
- @richfab made their first contribution in #94
- @Alessandro100 made their first contribution in #107
- @dersvenhesse made their first contribution in #124
- @jcpitre made their first contribution in #145
- @uwinkelvos made their first contribution in #157
- @DanielKerger made their first contribution in #172
- @davidgamez made their first contribution in #173
- @FinnHuelsbusch made their first contribution in #168
Full Changelog: v3.1.2...v4.0.0
v3.1.2
What's Changed
- Should be possible to link back to 1.0 feeds by @testower in #74
- Add IANA time zones by @leonardehrenfried in #75
New Contributors
- @leonardehrenfried made their first contribution in #75
Full Changelog: v3.1.1...v3.1.2
v3.1.1
v3.1.0
v2.3-RC2 is now official
With the V2.3 Release Candidate now official, this release removes the "RC2" from all files in the Json Schema. This has been done in #72 by @testower
Full Changelog: v3.0.3...v3.1.0
v3.0.3
What's Changed
- Fix type from number to integer by @isabelle-dr in #70
Full Changelog: v3.0.2...v3.0.3
v3.0.2
What's Changed
- Fix invalid json, no trailing commas by @testower in #63
- Add GitHub Actions to validate schemas by @AntoineAugusti in #54
- Create README.md by @isabelle-dr in #64
- Improved schema by @tdelmas in #66
- Update V2.3-RC to V2.3-RC2 by @isabelle-dr in #67
New Contributors
- @AntoineAugusti made their first contribution in #54
- @tdelmas made their first contribution in #66
Full Changelog: v3.0.1...v3.0.2
v3.0.1
v3.0.0
⚠️ This release is different from the previous ones ⚠️
⛔This isn't a GBFS v3.0 release candidate!⛔
The main change in this release is the way we organize this repository. Historically, we've been using Github Releases for new releases of the GBFS specification. We've decided to change this because:
- we can't fix errors in previous releases
- we want a quick and easy way of linking tools directly to the schemas
With this release, we're bringing a new organisation: the GBFS specification releases will be organized per folder and will be accessible in the master branch. The GitHub releases of this repository will be used to fix bugs, and add release candidates.
The release numbers will follow the semantic versioning: MAJOR.MINOR.PATCH.
The MAJOR number will be used for refactoring and any other changes that need our users to update the way they're using this product.
The MINOR number will be used for adding release candidates or making release candidates official.
The PATCH number will be used, well, for patches
We also took this opportunity to fix numerous small errors in the Json Schemas.
🎉 Shoutout to @PierrickP for making lots of corrections while building the gbfs-validator
We also included a schema for the GBFS v2.3 Release Candidate.
⚙️ Work
Everything is in #58
Thank you to @testower, @hannesj and @albertoabellagarcia for flagging errors!
v2.2
Improves system_pricing_plans.json