Pin sigil-tls 0.16.5 and drop the local redirect

Message

The handshake and request-write bounds need sigil-tls 0.16.5, which could not be pinned until it was tagged, so the pair was built through tls-redirects.sgl. That tag now exists, so the lock names the released version and the redirect goes in the same commit as the pin it stood in for.

Doing these together matters. Between the two, package.sgl asked for ^0.16.5 while the lock still named 0.16.4, whose tls-write takes two arguments where the new write loop passes four, so anyone resolving from the lock would have hit an arity error on every HTTPS request carrying a timeout.

Suite is 164 for 164 against the published dependency rather than the redirect.

Changed

 sigil.lock        |  6 +++---
 tls-redirects.sgl | 14 --------------
 2 files changed, 3 insertions(+), 17 deletions(-)

Diff

sigil.lockmodified

@@ -13,9 +13,9 @@

version: "0.16.0")

(package name: "sigil-tls"

url: "codeberg:sigil/sigil-tls"

−16

ref: "^0.16.0"

−17

sha: "baf05e45ed4090406c2990debadabfcd8253d834"

−18

version: "0.16.4")

+16

ref: "^0.16.5"

+17

sha: "fe4b756f2f46eacf5e3a4eb5d17f2681d88c5ee8"

+18

version: "0.16.5")

(package name: "sigil-json"

url: "codeberg:sigil/sigil-json"

ref: "^0.16.0"

tls-redirects.sgldeleted

@@ -1,14 +0,0 @@

−1

;; Local-only redirect used while sigil-tls 0.16.5 is unreleased.

−2

;;

−3

;; sigil-http's handshake and request-write bounds need sigil-tls 0.16.5,

−4

;; which cannot be pinned until it is tagged. This points ONLY sigil-tls at

−5

;; the sibling worktree so the pair can be built and tested together. It

−6

;; deliberately does NOT redirect codeberg:sigil/sigil, so the runtime stays

−7

;; the locked release rather than whatever the local monorepo is at.

−8

;;

−9

;; Delete this file once sigil-tls 0.16.5 is tagged and pinned in package.sgl.

−10

(redirects

−11

repos: (list

−12

(for-repo

−13

url: "codeberg:sigil/sigil-tls"

−14

use: (from-path dir: "../task-sigil-http-bound-every-blocking-segment-tls"))))