Skip to content

Releases: MobilityData/gbfs-json-schema

v4.0.0

14 Oct 20:10
ca29ba4

Choose a tag to compare

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

New Contributors

Full Changelog: v3.1.2...v4.0.0

v3.1.2

23 Aug 11:31
5273f96

Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v3.1.1...v3.1.2

v3.1.1

21 Apr 15:50
1d9bb2b

Choose a tag to compare

Patch

  • Update versions enum in gbfs_versions for 2.3 release by @testower in #73

v3.1.0

13 Apr 14:01
2cc87f0

Choose a tag to compare

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

12 Apr 23:06
5e02044

Choose a tag to compare

What's Changed

Full Changelog: v3.0.2...v3.0.3

v3.0.2

16 Mar 13:15
99a54d4

Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v3.0.1...v3.0.2

v3.0.1

25 Nov 13:55
4b1f5a4

Choose a tag to compare

Patch some of the conditionally required fields, done in #61

v3.0.0

23 Nov 13:00
60305d2

Choose a tag to compare

⚠️ 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

19 Apr 20:41

Choose a tag to compare

Improves system_pricing_plans.json

v2.1

30 Mar 15:12
904a80b

Choose a tag to compare

v2.1
#136 - Add vehicle type definitions
#219 - Add geofencing, virtual station, and dockless support
#261 - Aggregate available vehicle_types at a station