Repository navigation
chore: reconcile with upstream Tesla protos - #69
Draft
github-actions[bot] wants to merge 1 commit into
Draft
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
github-actions
Bot
force-pushed
the
upstream-reconcile
branch
from
October 19, 2026 06:54
bf626bb to
732bc56
Compare
github-actions
Bot
force-pushed
the
upstream-reconcile
branch
from
October 26, 2026 06:55
732bc56 to
5c14a43
Compare
This branch has not been deployed
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.
Advances
upstream.jsonto upstream HEAD. If CI's pinned coverage gatefails, merge the listed symbols into
proto/and add a changeset. If it'salready green, review any upstream overlap candidates below - upstream now
defines a symbol we previously carried as a local extension - then mark
ready for review.
Upstream coverage report (head mode)
teslamotors/vehicle-command @
fc5a1910ad45No coverage findings.
Upstream HEAD moved to
fc5a1910ad45with no change underpkg/protocol/protobuf- nothing to reconcile.teslamotors/fleet-telemetry @
bd076fe14948.telemetry.vehicle_data.CruiseStateValue(vehicle_data.proto) is not in upstream and has no TESLEMETRY-EXT marker.telemetry.vehicle_data.PowerTransferStatusValue(vehicle_data.proto) is not in upstream and has no TESLEMETRY-EXT marker.telemetry.vehicle_data.Value.cruise_state_value(vehicle_data.proto) is not in upstream and has no TESLEMETRY-EXT marker.telemetry.vehicle_data.Value.power_transfer_status_value(vehicle_data.proto) is not in upstream and has no TESLEMETRY-EXT marker.telemetry.vehicle_data.Field.AccRail(vehicle_data.proto) is not in upstream and has no TESLEMETRY-EXT marker.telemetry.vehicle_data.Field.PowerTransferStatus(vehicle_data.proto) is not in upstream and has no TESLEMETRY-EXT marker.telemetry.vehicle_data.Field.AutomaticEmergencyBrakingState(vehicle_data.proto) is not in upstream and has no TESLEMETRY-EXT marker.telemetry.vehicle_data.Field.RollingResistanceCoefficient(vehicle_data.proto) is not in upstream and has no TESLEMETRY-EXT marker.telemetry.vehicle_data.Field.CruiseState(vehicle_data.proto) is not in upstream and has no TESLEMETRY-EXT marker.telemetry.vehicle_data.Field.LifetimeDcChargeEnergyKwh(vehicle_data.proto) is not in upstream and has no TESLEMETRY-EXT marker.telemetry.vehicle_data.Field.VehicleMassKg(vehicle_data.proto) is not in upstream and has no TESLEMETRY-EXT marker.telemetry.vehicle_data.CarTypeValue.CarTypeSemiTruckV2(vehicle_data.proto) is not in upstream and has no TESLEMETRY-EXT marker.telemetry.vehicle_data.CarTypeValue.CarTypeCybercab(vehicle_data.proto) is not in upstream and has no TESLEMETRY-EXT markerFile changes vs pinned hashes:
vehicle_data.proto