From 452608b8a97d2f1e08816be2375b607968bb38ce Mon Sep 17 00:00:00 2001 From: meh Date: Wed, 9 Sep 2026 16:35:41 +0700 Subject: [PATCH] release: 0.1.36 Three commits landed after 0.1.35 and none of them bumped the version, so nothing would have been released and the published browser would stay built against the engine 0.1.35 resolved: 5fd2e24 stop committing lockfiles de0fac7 pin @solidjs/signals 367f594 the headless host action does not need a secret The first is the one that matters. 0.1.35 was built with a lockfile pinning ps-blitz 0.4.4; master now resolves 0.4.6, which is the difference between a browser that can intercept a router click and reach a TLS 1.3 host and one that cannot. The second changes the frontend bundle. The third touches only a composite action consumed at `@master`, and would not have justified a release on its own. This is the same gap as ps-blitz 0.4.6: master moved past its last release and the version said otherwise, so a consumer resolving by version got code nobody had shipped. --- Cargo.toml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Cargo.toml b/Cargo.toml index 6c81b02..71f1222 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -3,7 +3,7 @@ members = ["apps/chuzz", "crates/chuzz-control"] resolver = "3" [workspace.package] -version = "0.1.35" +version = "0.1.36" edition = "2024" rust-version = "1.91" license = "MIT OR Apache-2.0"