Repository navigation
Allow gtfs-realtime-bindings 3.x - #14
Merged
Merged
Conversation
Owner
|
Thanks @raman325. Can you rebase to pick up CI tests? |
Relax the exact ==2.0.0 pin to a >=2.0.0 floor. Bindings 3.0.0 only adds proto fields, and the test suite passes on both 2.0.0 and 3.0.0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
raman325
force-pushed
the
allow-gtfs-realtime-bindings-3
branch
from
October 10, 2026 14:49
0c6d572 to
dd7d1c3
Compare
Merged
Owner
|
0.4.3 is out |
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
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.
Summary
Relax
gtfs-realtime-bindings==2.0.0togtfs-realtime-bindings>=2.0.0.Why
py-nymta is the only package in Home Assistant core that pins
gtfs-realtime-bindings, so its exact pin decides the version for every HA install. Bindings 3.0.0 (released 2026-09-17) adds proto fields such asFeedEntity.stop,trip_modifications, StopTimeProperties pickup/drop-off types and vehiclewheelchair_accessible. Other libraries need those fields, and right now they can't be used in core alongside themtaintegration. I hit this with aiomobilitydatabase, the library behind the proposedmobilitydataintegration (home-assistant/core#177905). Under HA's 2.0.0 its realtime parsing fails withProtocol message FeedEntity has no "stop" field.A floor instead of
==3.0.0keeps the original HA-compatibility intent of #8 and still allows 2.0.0. It also avoids the same lockstep problem the next time the bindings release.Testing
py-nymta only parses
FeedMessage, and 3.0.0 doesn't change any existing fields, only adds new ones. The test suite passes on both versions:I left the version number alone so you can decide when to release. Once a release is out, I'm happy to open the core bump PR.
🤖 Generated with Claude Code