Lumen ChartsLumen Charts
Reference

Releases and upgrading

How to identify the exact runtime release and upgrade safely.

Download Markdown

These docs are built against one verified chart release. Its build ID appears above each article and matches the compiled runtime the demo uses.

Compatibility version versus build ID

The public version() string tells you which version line the runtime is compatible with. The SHA-256 runtime manifest identifies the exact wrapper, iframe, styles and optional Pine files served here. When you report a problem or compare deployments, use the manifest.

About this documentation release

This first release adds the integration guides, the public API reference, a demo that behaves the same every time, and replaceable local images. It doesn't change how the chart language works, and it doesn't introduce a new universal compatibility version.

There's only one runtime release for now, so there's no versions menu. As more supported runtime releases come out, their docs should keep stable URLs and include clear upgrade notes.

Upgrade safely

Upgrade the runtime, declarations, docs and optional files together as one release.

  1. Read the new release's compatibility and schema changes.
  2. Test your symbol metadata and your historical and realtime sample data.
  3. Test drawings, indicators and a sample of real saved layouts and templates.
  4. Try mounting, unmounting, reconnecting and failed save/load operations.
  5. Check every deployed file against the new release's manifest.
  6. Ship the whole release, and keep the previous one ready for rollback.

Don't mix versions

A new wrapper with an old inner runtime or Pine worker can fail during startup or when the two talk to each other. Versioned paths that never change prevent old and new files from mixing in caches. To roll back, restore the whole release, not just one JavaScript file.

Saved state

Keep provider and schema namespaces clearly separate. Reject saved data that isn't compatible, and never quietly drop parts of it. An older release may not be able to read data saved in a newer schema, so keep backups before any migration.

Schema policy

On this page