Skip to content

chore: reconcile with upstream Tesla protos - #69

Draft
github-actions[bot] wants to merge 1 commit into
mainfrom
upstream-reconcile
Draft

github-actions[bot] wants to merge 1 commit into
mainfrom
upstream-reconcile

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 12, 2026 •

Copy link
Copy Markdown
Contributor

Advances upstream.json to upstream HEAD. If CI's pinned coverage gate
fails, merge the listed symbols into proto/ and add a changeset. If it's
already 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 @ fc5a1910ad45

No coverage findings.

Upstream HEAD moved to fc5a1910ad45 with no change under pkg/protocol/protobuf - nothing to reconcile.

teslamotors/fleet-telemetry @ bd076fe14948

  • unmarked_extension: enum .telemetry.vehicle_data.CruiseStateValue (vehicle_data.proto) is not in upstream and has no TESLEMETRY-EXT marker
  • unmarked_extension: enum .telemetry.vehicle_data.PowerTransferStatusValue (vehicle_data.proto) is not in upstream and has no TESLEMETRY-EXT marker
  • unmarked_extension: field .telemetry.vehicle_data.Value.cruise_state_value (vehicle_data.proto) is not in upstream and has no TESLEMETRY-EXT marker
  • unmarked_extension: field .telemetry.vehicle_data.Value.power_transfer_status_value (vehicle_data.proto) is not in upstream and has no TESLEMETRY-EXT marker
  • unmarked_extension: enum value .telemetry.vehicle_data.Field.AccRail (vehicle_data.proto) is not in upstream and has no TESLEMETRY-EXT marker
  • unmarked_extension: enum value .telemetry.vehicle_data.Field.PowerTransferStatus (vehicle_data.proto) is not in upstream and has no TESLEMETRY-EXT marker
  • unmarked_extension: enum value .telemetry.vehicle_data.Field.AutomaticEmergencyBrakingState (vehicle_data.proto) is not in upstream and has no TESLEMETRY-EXT marker
  • unmarked_extension: enum value .telemetry.vehicle_data.Field.RollingResistanceCoefficient (vehicle_data.proto) is not in upstream and has no TESLEMETRY-EXT marker
  • unmarked_extension: enum value .telemetry.vehicle_data.Field.CruiseState (vehicle_data.proto) is not in upstream and has no TESLEMETRY-EXT marker
  • unmarked_extension: enum value .telemetry.vehicle_data.Field.LifetimeDcChargeEnergyKwh (vehicle_data.proto) is not in upstream and has no TESLEMETRY-EXT marker
  • unmarked_extension: enum value .telemetry.vehicle_data.Field.VehicleMassKg (vehicle_data.proto) is not in upstream and has no TESLEMETRY-EXT marker
  • unmarked_extension: enum value .telemetry.vehicle_data.CarTypeValue.CarTypeSemiTruckV2 (vehicle_data.proto) is not in upstream and has no TESLEMETRY-EXT marker
  • unmarked_extension: enum value .telemetry.vehicle_data.CarTypeValue.CarTypeCybercab (vehicle_data.proto) is not in upstream and has no TESLEMETRY-EXT marker

File changes vs pinned hashes:

  • changed: vehicle_data.proto

@coderabbitai

coderabbitai Bot commented Oct 12, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Central YAML; Path: .coderabbit.yaml
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 1405fbdf-06dc-4c0b-8a5f-9b11dc00082d

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Comment @coderabbitai help to get the list of available commands.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants