Skip to content

Bump karoo-ext 1.1.7 → 1.1.8#6

Open
lgangitano wants to merge 1 commit into
yrkan:mainfrom
lgangitano:chore/karoo-ext-1.1.8-bump
Open

Bump karoo-ext 1.1.7 → 1.1.8#6
lgangitano wants to merge 1 commit into
yrkan:mainfrom
lgangitano:chore/karoo-ext-1.1.8-bump

Conversation

@lgangitano
Copy link
Copy Markdown

Bumps the Karoo Extension SDK from 1.1.7 to 1.1.8.

1.1.8 adds the DataType.Type.CLIMB stream (PR #72 upstream, @brentnd) — exposing DISTANCE_TO_TOP / ELEVATION_TO_TOP etc. — which the CLIMBER-integration and W'-chart work build on.

Single-line dependency change; no behavioural change on its own.

(Re-opened as a fresh PR: the previous one — #3 — was auto-closed when I force-pushed this branch during an unrelated commit-author cleanup, which briefly orphaned its history from main. The branch is now replanted cleanly on current main.)

Brings in upstream PR hammerheadnav/karoo-ext#72 (January 2026):

- Exports the CLIMB DataType (TYPE_CLIMB_ID) with fields
  DISTANCE_FROM_BOTTOM, DISTANCE_TO_TOP, ELEVATION_FROM_BOTTOM,
  ELEVATION_TO_TOP, CLIMB_ELEVATION — driven by Karoo's native
  Climber detection on routes and freestyle rides.
- Exports CLIMB_NUMBER, SEGMENT_ELEVATION_REMAINING, DESCENT_REMAINING.
- Fixes the ELEVATION_REMAINING field-name mismatch reported in
  upstream issue #71 (was emitting FIELD_ASCENT_REMAINING_ID under
  FIELD_ELEVATION_REMAINING_ID's umbrella since 1.1.7).

KOS requirement moves from 1.594.2280+ to 1.613.2351+ accordingly;
listed in the PR body for users running older KOS releases.

No behavioral change in this PR — only the dependency version. Follow-up
PRs will subscribe to the newly-exported CLIMB stream and adapt
ClimbDataService accordingly.
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.

1 participant