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

Patch

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

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

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

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

v2.1

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

v2.0

Change booleans from 1/0 to true/false
Rotate bike_id