Take twill 1.13.0

.github/workflows/ci.yml

@@ -84,10 +84,10 @@ jobs:
       # would have. Pinned rather than floating: a green run should mean this
       # code passed against a known compiler, not against whatever was newest
       # that morning.
-      - name: Install twill v1.12.0
+      - name: Install twill v1.13.0
         run: |
           curl -fsSL -o twill \
-            https://github.com/twill-lang/twill/releases/download/v1.12.0/twill-v1.12.0-linux-amd64
+            https://github.com/twill-lang/twill/releases/download/v1.13.0/twill-v1.13.0-linux-amd64
           chmod +x twill
           ./twill --version
 

CHANGELOG.md

@@ -5,9 +5,17 @@ cannot point at.
 
 ## Unreleased
 
-Seventeen commits since `v0.1.0`, all of them either following twill's releases
+Eighteen commits since `v0.1.0`, all of them either following twill's releases
 or fixing what following them exposed.
 
+### Take twill 1.13.0
+
+twill 1.13.0 is released, so the pin follows it. `spool.toml`, CI and the
+README install line move from 1.12.0 to 1.13.0. The compile floor stays 1.12.0,
+because the tuple returns this code relies on arrived there and nothing newer is
+used; the pin sits one release ahead of the floor, and the spool comment says
+so. No source or test changed and the six suites pass unchanged on 1.13.0.
+
 ### The glyph tables are `const`, and a low and a high come back as a tuple
 
 `docs/needs.md` entries 9 and 13 were open and twill had delivered both. `HEX`,
@@ -21,7 +29,8 @@ callers destructure the pair. The `Span` and `Range` structs are gone; they were
 two of the four single-use type names entry 13 complained about. The heatmap
 functions that took a `Range` take `lo` and `hi`.
 
-The minimum twill is 1.12.0 now, in `spool.toml`, in CI and in the README. The
+The compile floor is twill 1.12.0, which is what `spool.toml`, CI and the README
+recorded at this point; the pin later followed the release past it, above. The
 six suites pass unchanged, which is the point: nothing a test could see moved.
 
 ### The minimum twill is now 1.7.0, and it is load-bearing

README.md

@@ -61,9 +61,9 @@ open.
 # Assets: linux-amd64, linux-arm64, darwin-amd64, darwin-arm64,
 # windows-amd64.exe.
 curl -fsSL -o twill \
-  https://github.com/twill-lang/twill/releases/download/v1.12.0/twill-v1.12.0-linux-amd64
+  https://github.com/twill-lang/twill/releases/download/v1.13.0/twill-v1.13.0-linux-amd64
 chmod +x twill
-./twill --version        # Twill 1.12.0
+./twill --version        # Twill 1.13.0
 
 git clone https://github.com/twill-lang/weft && cd weft
 ../twill test tests

spool.toml

@@ -10,7 +10,8 @@ entry = "src/chart.tw"
 # The entry stays because the floor is real. `src/scale.tw` and
 # `src/heatmap.tw` return a tuple, which arrived in 1.12.0, and the glyph
 # tables are `const`, which arrived in 1.10.0, so `^1.12.0` is the minimum this
-# code actually compiles under rather than the newest release at the time of
-# writing. See the note in README.md and docs/needs.md.
+# code actually compiles under. The pin follows the twill release past that
+# floor, so it reads `^1.13.0`; 1.12.0 stays the real floor. See the note in
+# README.md and docs/needs.md.
 [dependencies]
-twill = { version = "^1.12.0", git = "https://github.com/twill-lang/twill" }
+twill = { version = "^1.13.0", git = "https://github.com/twill-lang/twill" }