Blog post for v0.21

blog/2025-09-24-temporal-release/index.md

@@ -23,13 +23,15 @@ Currently, `temporal_rs` v0.1 is being used by Boa, [Kiesel][kiesel-site],
 [V8][v8-site], and [Yavashark][yavashark-repo] for their Temporal
 implementations (more on that later) and is [estimated](https://chromestatus.com/feature/5668291307634688) to land unflagged in **Chromium v144**.
 
+<!-- truncate -->
+
 ### Why v0.1? Why not v1.0?
 
-Right now the [Temporal proposal](https://github.com/tc39/proposal-temporal) is at Stage 3 (4 being the final stage) in the standards process. Although unlikely, 
-we want to remain on a minor version to catch any changes which come in (mostly bug fixes) before the proposal reaches stage 4 
-and thus complete. We expect that to happen in Q1 2026. 
+Right now the [Temporal proposal](https://github.com/tc39/proposal-temporal) is at Stage 3 (4 being the final stage) in the standards process. Although unlikely,
+we want to remain on a minor version to catch any changes which come in (mostly bug fixes) before the proposal reaches stage 4
+and thus complete. We expect that to happen in Q1 2026.
 
-Fear not! temporal_rs passes over 4000 specification tests, is stable and ready to use. 
+Fear not! temporal_rs passes over 4000 specification tests, is stable and ready to use.
 
 To celebrate the release of `temporal_rs`, we'll cover a short
 background of the Temporal implementation in Boa and why `temporal_rs`