build(deps): bump Tracking compat to 3#77
Merged
Conversation
Tracking v3 makes the multi-band `track!` band-measurement keys case-sensitive: the named-tuple keys must match the `TrackState`'s band set (derived from each signal's `band_key`, i.e. `:L1`/`:L5`). Update the Flexiband III-7a integration test to pass `L1`/`L5` instead of `l1`/`l5`. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #77 +/- ##
=======================================
Coverage 98.15% 98.15%
=======================================
Files 14 14
Lines 1520 1520
=======================================
Hits 1492 1492
Misses 28 28 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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
1 participant
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.
Bumps the
Trackingcompat entry from2to3(test-only dependency in[extras]/[targets]).Supersedes #73, which CompatHelper opened as
"2, 3". Per request, this pins to3only.Why CI was failing
Under
"2, 3"the resolver picks Tracking v3, which makes the multi-bandtrack!band-measurement keys case-sensitive — the named-tuple keys must match theTrackState's band set (derived from each signal'sband_key, i.e.:L1/:L5):The Flexiband III-7a integration test passed lowercase
l1/l5keys. Updated toL1/L5.🤖 Generated with Claude Code