routing_bloc 0.4.8

Route lifecycle state machine (idle / loading / active / error) with glanceable progress UI. Works with any routing_engine backend.

0.4.8

Documentation only. No code change.

Comments and documentation that used this project's internal shorthand now say the same thing in plain words. Where earlier entries in this changelog used that shorthand, they were reworded; no fact in them changed.

• analysis_options.yaml: the comment above the analyzer's strict modes now says what the modes do, instead of pointing at an internal review note.
• MAINTENANCE_MODE.md: rewritten in plain words. Two statements in it were out of date and are corrected: it said the README and the pub.dev listing state the maintenance status (they do not; the file now says so), and its pinning example named 0.3.x, the line current when it was written (it now names the current line, 0.4.x). The status itself is unchanged.
• CHANGELOG.md: the 0.3.0 entry.

Apart from pubspec.yaml (the version), analysis_options.yaml (one comment), MAINTENANCE_MODE.md and this changelog, the published files are identical to 0.4.7.

0.4.7

flutter pub get inside the published package, and in its example, now works. No code change.

The published 0.4.6 carried development-only overrides in two files, pointing at folders that exist only in this package's source repository:

• pubspec.yaml: ../navigation_safety and ../navigation_safety_core. flutter pub get inside the downloaded package failed with exit code 66 ("depends on navigation_safety_core from path which doesn't exist").
• example/pubspec.yaml: 28 path: ../../<package> overrides, with the same failure in example/ ("depends on voice_guidance from path which doesn't exist"). Under them, the example also required navigation_safety: ^0.5.0, and no 0.5.x of navigation_safety has ever been published (it went from 0.4.0 to 0.7.0), so the example could not have resolved even without the overrides.

Apps that depend on routing_bloc were not affected: checked, an app depending on routing_bloc: 0.4.6 resolves normally.

The package's overrides now live in pubspec_overrides.yaml, which pub does not publish; the example's live in example/pubspec_overrides.yaml, which .pubignore keeps out. The example now requires the ranges this package itself declares: navigation_safety: ^0.9.0 and routing_engine: '>=0.4.0 <0.7.0'. Apart from pubspec.yaml, example/pubspec.yaml and this changelog, the published files are identical to 0.4.6.

0.4.6

• Widen latlong2 from ^0.9.1 to >=0.9.1 <0.11.0.

  latlong2 0.10.0 shipped 2026-04-25 and flutter_map 8.x resolves it, so the old ceiling made this package uninstallable alongside current flutter_map — version solving failed for every published version. No source change; the cap was gratuitous. Verified on latlong2 0.10.1: analyze clean, 53/53 tests pass.

Changelog

0.4.5

• Widen the routing_engine constraint to >=0.4.0 <0.7.0 so this package can resolve alongside routing_engine 0.6.0 and route_condition_forecast 0.2.0.

  routing_engine 0.6.0 fixes a safety defect: RouteManeuver.position was silently returning const LatLng(0, 0) — Null Island, a real coordinate in the Gulf of Guinea — for a maneuver whose location failed to parse. It is now nullable. This package's lib/ reads no maneuver position, so 0.6.0 is source-compatible and this is a PATCH release, not a breaking one.

  The widen is not cosmetic: for a 0.x package a caret does not admit the next minor, so without it route_condition_forecast 0.2.0 (which pins >=0.6.0) and this package had an EMPTY intersection — a consumer combining a routing bloc with route condition forecasting would have hit a hard version solving failed.

• The example app now guards the nullable position: a maneuver with no location is not given a substitute coordinate.

0.4.4

• Widen the routing_engine constraint to >=0.4.0 <0.6.0 so consumers can take routing_engine 0.5.0 (language-honoring turn-by-turn narration) alongside routing_bloc. No library code change (lib/ is byte-identical to 0.4.3).

0.4.3

• docs: correct stale README install pin to current version (no API change).

0.4.2

• Republish from the embedded-target Dart 3.10.1 SDK (Flutter 3.38.3) to correct a stale ^3.11.0 SDK floor in the previously-published artifact. No source or behavior change; the source already declared sdk: ^3.10.0. Restores pub get for embedded/automotive Dart consumers on Dart 3.10.x.

0.4.1 — 2026-05-10 — Refresh stale dependency constraints

• Bump navigation_safety: ^0.5.0 → ^0.9.0 (was 7-day-stale).
• Bump routing_engine: ^0.3.0 → ^0.4.0 (consumer-side refresh matching the routing_engine 0.4.0 release earlier the same day).
• No source changes; pubspec dep-constraint refresh only. The monorepo dependency_overrides: block was masking the staleness locally; pana resolves against pub.dev (no overrides) and was penalizing the 0.4.0 release accordingly.

0.4.0 — 2026-05-10 — Pana score recovery + dart format alignment

• Trim pubspec description to ≤180 characters so search-engine snippets surface the package's purpose cleanly.
• Apply dart format across lib/ and test/ (15 files reformatted) to clear pana static-analysis formatter findings.
• No SDK source changes; metadata + formatter pass only.

0.3.0

• Harmonize package version to 0.3.0, in step with the other packages in this repository.
• Align internal ecosystem dependency constraints to ^0.3.0 where applicable.
• No breaking API changes in this package for this release.