@rootnative/inertia-svg 0.0.3 → 0.0.4

package/CHANGELOG.md

@@ -1,11 +1,15 @@
 # Changelog
 
-All notable changes to `@rootnative/inertia-svg` are documented here. The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and the project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). Pre-`1.0`, breaking changes may land in minor versions and are called out under their release.
+All notable changes to `@rootnative/inertia-svg` are documented here. The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and the project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). Pre-`1.0.0`, breaking changes may land in minor versions and are called out under their release.
 
 This package ships in lockstep with `@rootnative/inertia` — version numbers track the core release that introduced or last touched the adapter.
 
 ## [Unreleased]
 
+## [0.0.4] - 2026-07-29
+
+**Lockstep version bump** alongside `@rootnative/inertia@0.0.4` (`boxShadow` on the `animate` surface, plus window-coordinate measurement and a style carry for `layoutId` shared-element transitions). No runtime changes in this adapter; the `@rootnative/inertia` peer range moves to `>=0.0.4`.
+
 ## [0.0.3] - 2026-07-25
 
 **Lockstep version bump** alongside `@rootnative/inertia@0.0.3` (correctness fixes to the resting-value base, `<Presence>` ordering and unmount, endless-repeat completion counters, `useColorCascade`, `useAnimator`, and the `layoutId` registry). No runtime changes in this adapter; the `@rootnative/inertia` peer range moves to `>=0.0.3`.
@@ -29,16 +33,18 @@ This package ships in lockstep with `@rootnative/inertia` — version numbers tr
 
 Lockstep version bump alongside `@rootnative/inertia@0.0.0-alpha.1` (README / `llms.txt` updates only; no runtime changes).
 
-## [0.0.0-alpha.0]
+## 0.0.0-alpha.0
+
+_No git tag was cut for this release; the published artifact is on npm as [`@rootnative/inertia-svg@0.0.0-alpha.0`](https://www.npmjs.com/package/@rootnative/inertia-svg/v/0.0.0-alpha.0). Unlinked here for that reason — every other heading resolves to a real tag._
 
 ### Added
 
 - `MotionPath` over `react-native-svg`. Animatable: `d` (element-wise scalar interpolation on structurally-compatible paths), `fill`, `stroke`, `strokeWidth`, opacities, `strokeDashoffset`. Source and target paths must share the same command sequence after implicit-repeat expansion; remount with `key` to switch shape.
 
-[unreleased]: https://github.com/rootnative/inertia/compare/core+gestures+gradients+svg@0.0.3...HEAD
+[unreleased]: https://github.com/rootnative/inertia/compare/core+gestures+gradients+svg@0.0.4...HEAD
+[0.0.4]: https://github.com/rootnative/inertia/releases/tag/core+gestures+gradients+svg@0.0.4
 [0.0.3]: https://github.com/rootnative/inertia/releases/tag/core+gestures+gradients+svg@0.0.3
 [0.0.2]: https://github.com/rootnative/inertia/releases/tag/core+gestures+gradients+svg@0.0.2
 [0.0.1]: https://github.com/rootnative/inertia/releases/tag/core+gestures+gradients+svg@0.0.1
 [0.0.0-alpha.2]: https://github.com/rootnative/inertia/releases/tag/core+gestures+gradients+svg@0.0.0-alpha.2
 [0.0.0-alpha.1]: https://github.com/rootnative/inertia/releases/tag/core+gestures+gradients+svg@0.0.0-alpha.1
-[0.0.0-alpha.0]: https://github.com/rootnative/inertia/releases/tag/core+gestures+gradients+svg@0.0.0-alpha.0

package/README.md

@@ -79,7 +79,7 @@ transition={{
 
 In dev, the component throws on template mismatches at mount, when `animate.d` changes shape, or when the static `d` prop itself changes shape between renders. In production those errors degrade to a no-op snap so a single bad target doesn't crash the screen.
 
-Path resampling between structurally different shapes (flubber-style) is out of scope for v0.2. For arbitrary shape swaps, remount with `key={...}`.
+Path resampling between structurally different shapes (flubber-style) is out of scope by design. For arbitrary shape swaps, remount with `key={...}`.
 
 ## Shapes — MotionCircle, MotionRect, MotionLine
 
@@ -127,7 +127,7 @@ const MotionEllipse = createMotionSvgComponent(Ellipse, {
 
 All primitives participate in `<MotionConfig reducedMotion>` just like the core ones — when the OS reduce-motion setting is on (or you pass `reducedMotion="always"`), every animated property snaps directly to its target.
 
-## What this package doesn't do (v0.2)
+## What this package doesn't do
 
 - Path resampling between arbitrary shapes.
 - Morphing an `L` into a `C` (or other across-command interpolation). Element-wise scalar interpolation is intentional.

package/dist/index.d.mts

@@ -258,7 +258,7 @@ declare const MotionLine: react.ComponentType<MotionSvgComponentProps<react_nati
  * and when `animate.d` changes; the worklet only ever consumes flat number
  * arrays + a frozen command template.
  *
- * Path morphing in v0.2 requires **structural compatibility**: the source and
+ * Path morphing requires **structural compatibility**: the source and
  * every target `d` must produce the same command sequence (same command
  * letters, in the same order, after implicit-repeat expansion). Element-wise
  * numeric interpolation is the entire morphing model — we do not resample

package/dist/index.d.ts

@@ -258,7 +258,7 @@ declare const MotionLine: react.ComponentType<MotionSvgComponentProps<react_nati
  * and when `animate.d` changes; the worklet only ever consumes flat number
  * arrays + a frozen command template.
  *
- * Path morphing in v0.2 requires **structural compatibility**: the source and
+ * Path morphing requires **structural compatibility**: the source and
  * every target `d` must produce the same command sequence (same command
  * letters, in the same order, after implicit-repeat expansion). Element-wise
  * numeric interpolation is the entire morphing model — we do not resample

package/llms.txt

@@ -80,7 +80,7 @@ To switch between structurally different shapes, **remount with a new `key`**:
 />
 ```
 
-Path normalization that resamples between arbitrary shapes (the flubber-style approach) is out of scope for v0.2.
+Path normalization that resamples between arbitrary shapes (the flubber-style approach) is out of scope by design.
 
 ## Animatable props
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rootnative/inertia-svg",
-  "version": "0.0.3",
+  "version": "0.0.4",
   "description": "Animatable SVG primitives (path morphing, fill/stroke) for @rootnative/inertia, built on react-native-svg.",
   "license": "MIT",
   "author": "RootNative",
@@ -50,7 +50,7 @@
     "!**/*.test.*"
   ],
   "peerDependencies": {
-    "@rootnative/inertia": ">=0.0.3",
+    "@rootnative/inertia": ">=0.0.4",
     "react": ">=19.0.0",
     "react-native": ">=0.81.0",
     "react-native-reanimated": ">=4.0.0",
@@ -69,7 +69,7 @@
     "react-test-renderer": "19.1.0",
     "tsup": "^8.3.5",
     "typescript": "^5.7.3",
-    "@rootnative/inertia": "0.0.3"
+    "@rootnative/inertia": "0.0.4"
   },
   "publishConfig": {
     "access": "public"

package/src/path.ts

@@ -4,7 +4,7 @@
  * and when `animate.d` changes; the worklet only ever consumes flat number
  * arrays + a frozen command template.
  *
- * Path morphing in v0.2 requires **structural compatibility**: the source and
+ * Path morphing requires **structural compatibility**: the source and
  * every target `d` must produce the same command sequence (same command
  * letters, in the same order, after implicit-repeat expansion). Element-wise
  * numeric interpolation is the entire morphing model — we do not resample