Versions and support

React Native Image Marker maintains independent documentation and release lines so Core v2 can evolve while existing v1 applications continue receiving critical fixes.

Package or line	Status	Documentation	Install
Core 2.1.x	Current release	v2 documentation	npm install react-native-image-marker@^2.1
Editor 0.3.x	Current optional editor	Editor guide	npm install react-native-image-marker-editor@^0.3
Recipe 0.1.x	Current document contract	Recipe guide	npm install @image-marker/recipe@^0.1
Node 0.1.x	Current server renderer	Node guide	npm install @image-marker/node@^0.1 sharp@^0.35
CLI 0.1.x	Current automation interface	CLI guide	npm install -g @image-marker/cli@^0.1
v1 LTS (1.12.x)	Current maintenance line	v1 documentation	npm install react-native-image-marker@1
v1.0.0	Immutable archive	v1.0.0 archive	npm install react-native-image-marker@1.0.0

Recipe, Node, CLI, and Editor are pre-1.0 packages with explicit version ranges. Their release notes identify API changes; lock a compatible minor range in production and upgrade intentionally.

v1 LTS commitment

v1 receives security, crash, serious correctness, platform compatibility, and documentation fixes for at least 12 months after v2 becomes generally available. An end-of-life date will be announced at least three months in advance. The v1 documentation remains online after maintenance ends.

New features and breaking changes belong to v2. Fixes are developed directly against release/1.x and forward-ported to v2 when applicable.

Why v1.0.0 does not change

The v1.0.0 tag, its locked archive branch, and its archive page preserve the original release. Published artifacts and tags are never rewritten. Users who need a v1 bug fix should upgrade within the compatible v1 line rather than expecting the original 1.0.0 package to change.