From ef263b328ef0bc8d5f64837ff565b7fbd32caed2 Mon Sep 17 00:00:00 2001
From: Baptiste Parmantier <baptiste.parmantier.pro@gmail.com>
Date: Tue, 29 Sep 2026 20:29:34 +0200
Subject: [PATCH 1/2] chore(release): 0.8.0
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The version lives in `[workspace.package]` and the three internal dependency
pins, all in the root manifest, so this is four lines and the lockfile.

0.8 rather than 0.7.2: under cargo's 0.x rules a minor bump is the breaking
one, and this cycle added public fields to structs consumers can build by
literal — `Camera.motion_blur`, `CameraKeyframePoint.easing`,
`BuiltScene.ghost_principal` — and changed what `motion_blur mode: "smear"`
emits, from an axis-aligned `Blur` to a `DirectionalBlur` oriented along the
velocity.

The README claimed 30 skill rules, and the install line claimed 29. There are
84. The counter stopped tracking three batches ago.

`#[deprecated(since = "0.7.1")]` attributes are left alone: they date the
deprecation, and moving them forward would erase when it happened.
---
 Cargo.lock | 8 ++++----
 Cargo.toml | 8 ++++----
 README.md  | 4 ++--
 3 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/Cargo.lock b/Cargo.lock
index 8c2803f..69c084b 100644
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -6575,7 +6575,7 @@ dependencies = [
 
 [[package]]
 name = "rustmotion"
-version = "0.7.1"
+version = "0.8.0"
 dependencies = [
  "clap",
  "clap_complete",
@@ -6613,7 +6613,7 @@ dependencies = [
 
 [[package]]
 name = "rustmotion-components"
-version = "0.7.1"
+version = "0.8.0"
 dependencies = [
  "dashmap",
  "gif 0.13.3",
@@ -6632,7 +6632,7 @@ dependencies = [
 
 [[package]]
 name = "rustmotion-core"
-version = "0.7.1"
+version = "0.8.0"
 dependencies = [
  "cosmic-text",
  "dashmap",
@@ -6654,7 +6654,7 @@ dependencies = [
 
 [[package]]
 name = "rustmotion-html"
-version = "0.7.1"
+version = "0.8.0"
 dependencies = [
  "html5ever 0.39.0",
  "markup5ever_rcdom 0.39.0+unofficial",
diff --git a/Cargo.toml b/Cargo.toml
index 4febefc..07fbd74 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -12,15 +12,15 @@ members = [
 # par dépendance interne — et une seule oubliée fait échouer la publication après
 # que les précédentes soient parties, ce qui ne se rattrape pas.
 [workspace.package]
-version = "0.7.1"
+version = "0.8.0"
 
 # Les dépendances internes portent aussi la version, donc elles se déclarent ici
 # pour la même raison. `path` sert au développement, `version` à ce que cargo
 # écrit dans le paquet publié : les deux doivent coexister, et rester d'accord.
 [workspace.dependencies]
-rustmotion-core = { path = "crates/rustmotion-core", version = "0.7.1" }
-rustmotion-components = { path = "crates/rustmotion-components", version = "0.7.1" }
-rustmotion-html = { path = "crates/rustmotion-html", version = "0.7.1" }
+rustmotion-core = { path = "crates/rustmotion-core", version = "0.8.0" }
+rustmotion-components = { path = "crates/rustmotion-components", version = "0.8.0" }
+rustmotion-html = { path = "crates/rustmotion-html", version = "0.8.0" }
 
 # Optimize dependencies even in dev builds. Our own crates stay at opt-level 0
 # (fast incremental + debuggable), but heavy compute in deps (image encoding,
diff --git a/README.md b/README.md
index 143d80e..fcb47e8 100644
--- a/README.md
+++ b/README.md
@@ -82,13 +82,13 @@ rustmotion info scenario.json
 
 ## Claude Code Skills
 
-rustmotion ships with built-in [Claude Code](https://claude.ai/claude-code) skills — 30 rules and best practices for generating video scenarios with AI. After installing rustmotion, run:
+rustmotion ships with built-in [Claude Code](https://claude.ai/claude-code) skills — 84 rules and best practices for generating video scenarios with AI. After installing rustmotion, run:
 
 ```bash
 # Install skills in your video project (recommended)
 cd my-video-project/
 rustmotion skills install
-# → .claude/skills/rustmotion/  (SKILL.md + 29 rules)
+# → .claude/skills/rustmotion/  (SKILL.md + 84 rules)
 # → CLAUDE.md                   (project instructions)
 
 # Or install globally (available in all projects)

From 94f3643c8e4c81468d69cfd7fc55e8bb9d4cffb8 Mon Sep 17 00:00:00 2001
From: Baptiste Parmantier <baptiste.parmantier.pro@gmail.com>
Date: Tue, 29 Sep 2026 20:34:07 +0200
Subject: [PATCH 2/2] chore(deps): move off the yanked unicode-segmentation
 1.13.1

The 0.8.0 publish dry-run surfaced it: `unicode-segmentation v1.13.1 in
Cargo.lock is yanked in registry crates-io`, pulled in transitively by
`cosmic-text` and by `ratatui`. 1.13.3 is the current compatible release and
needs no manifest change, only the lockfile.

Publishing over a yanked dependency succeeds and hands the problem to whoever
installs from the lockfile afterwards. The dry-run is now warning-free.
---
 Cargo.lock | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Cargo.lock b/Cargo.lock
index 69c084b..c1ec414 100644
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -8370,9 +8370,9 @@ checksum = "383ad40bb927465ec0ce7720e033cb4ca06912855fc35db31b5755d0de75b1ee"
 
 [[package]]
 name = "unicode-segmentation"
-version = "1.13.1"
+version = "1.13.3"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "da36089a805484bcccfffe0739803392c8298778a2d2f09febf76fac5ad9025b"
+checksum = "c6f5d3c3b1bf09027a88a6bc961fc00497d651009560b5463668dc81b0fa87a8"
 
 [[package]]
 name = "unicode-truncate"