16. v0.8.11 — History stability & public Piner

Released 2026-08-21. This patch keeps historical chart navigation stable through older-bar loading and moves the Pine engine to public npm. Follows v0.8.10.

Changed

• Piner now installs from public npm. Fractal Chart consumes the exact @heyphat/piner version 0.12.0 through the existing piner npm alias. Contributors and deployments no longer need a GitHub Packages registry mapping or NODE_AUTH_TOKEN.
• Alert names use a consistent raw-input limit. The 120-character maximum is checked before surrounding whitespace is trimmed for storage.
• Webhook delivery is easier to test and integrate. The injected fetch dependency now requires only the callable request signature used by delivery, without browser-specific static properties. Runtime delivery behavior is unchanged.

Fixed

• The first older-history load preserves the user's viewport. Initial chart setup no longer reapplies the time-scale offset during the first backfill, so the chart remains on the historical candles being viewed instead of jumping to realtime.
• Trackpad momentum wins over queued range restoration. Range writes remain identified as programmatic until Lightweight Charts applies them on its next animation frame, while each physical wheel event is captured after the chart processes it.
• Pointer and keyboard navigation remain deliberate. Mouse dragging and focused-pane arrow shortcuts update or clear the historical anchor just like wheel input, so navigating back to realtime is not mistaken for an accidental jump.
• History requests start only from user navigation. Initial layout and unrelated programmatic range changes cannot trigger pagination. Requests are deduplicated while one page is loading and re-armed after prepended data is applied.
• Historical refreshes stay anchored. Older-bar prepends, realtime updates, indicator refreshes, and visual-setting changes preserve the current historical window unless the user explicitly chooses Go to or Reset.

Verification

• Physical macOS trackpad verification confirmed that the first older-bar load remains at the user's historical position.
• The complete automated suite, TypeScript check, production build, and delayed rendered first-load regressions passed before release preparation.

Next steps

Back to the release list.

Next: Release Notes