From 0ec5937d4b6448dbe483a5677b26c5c3d49d18c3 Mon Sep 17 00:00:00 2001 From: o-murphy Date: Mon, 5 Oct 2026 14:37:03 +0300 Subject: [PATCH] build(pins): bump emsdk to 6.0.11 --- CHANGELOG.md | 4 ++++ docker/webassembly.Dockerfile | 10 +++++----- 2 files changed, 9 insertions(+), 5 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 4016f17..65b516c 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -7,6 +7,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 ## [Unreleased] +### Changed + +- **emsdk `6.0.9`/`f04ea239` -> `6.0.11`/`f6264d4a`** (`docker/webassembly.Dockerfile`), the pin [0046]'s weekly checker reported behind. sha256 recomputed from the real tarball; layout re-checked with `tar tJf` (still a top-level `install/` with `bin/`). + ## [0.7.4] - 2026-09-29 ### Changed diff --git a/docker/webassembly.Dockerfile b/docker/webassembly.Dockerfile index 80ebe56..02baee6 100644 --- a/docker/webassembly.Dockerfile +++ b/docker/webassembly.Dockerfile @@ -76,9 +76,9 @@ # URL below and compares it against emsdk's own `latest` alias. That is # exactly how this pin was found behind and moved. # -# The pinned version is the emscripten-releases-tags.json alias "6.0.9", +# The pinned version is the emscripten-releases-tags.json alias "6.0.11", # recorded as the value it resolved to when pinned, not the literal -# string "latest". `f04ea239d533260dd1db760dd2d668d5f9a88d6b` in the URL +# string "latest". `f6264d4a4dd9ba24a9f0a5702835a44d1463de13` in the URL # is the emscripten-releases build hash that alias resolved to; the URL # itself follows emsdk's own # emscripten_releases_download_url_template @@ -139,7 +139,7 @@ RUN apt-get update && apt-get install -y --no-install-recommends \ nodejs \ && rm -rf /var/lib/apt/lists/* -# emsdk 6.0.9, linux-x64 -- verified live before repinning here, the same +# emsdk 6.0.11, linux-x64 -- verified live before repinning here, the same # way the version before it was: downloaded the real tarball, computed # this exact sha256 locally, and inspected its own internal layout with # `tar tJf` (a top-level `install/` directory containing @@ -154,8 +154,8 @@ RUN apt-get update && apt-get install -y --no-install-recommends \ # build-platforms.toml deliberately records *no* emsdk version, because # MicroPython's own tools/ci.sh has never pinned one. RUN curl -fsSL -o /tmp/wasm-binaries.tar.xz \ - https://storage.googleapis.com/webassembly/emscripten-releases-builds/linux/f04ea239d533260dd1db760dd2d668d5f9a88d6b/wasm-binaries.tar.xz && \ - echo "d5c6c2917fbc1cae1a7d1e581f1c0b2817369dd57f94c7a0d05921476f1a7287 /tmp/wasm-binaries.tar.xz" | sha256sum -c - && \ + https://storage.googleapis.com/webassembly/emscripten-releases-builds/linux/f6264d4a4dd9ba24a9f0a5702835a44d1463de13/wasm-binaries.tar.xz && \ + echo "cab251b54999e8fb4260080f0e719796336570396e118865013a20b8d93dbb83 /tmp/wasm-binaries.tar.xz" | sha256sum -c - && \ mkdir -p /opt/emsdk && \ tar -xJf /tmp/wasm-binaries.tar.xz -C /opt/emsdk && \ rm /tmp/wasm-binaries.tar.xz && \