docker image bump - #1583
Merged
Merged
Conversation
thewtex
commented
Aug 10, 2026
thewtex
commented
Member
- feat(itk-wasm-cli): update default Docker image for 20260810-f8e99da52
- chore(itk-wasm): bump version to 1.0.0-b.200
- chore(pnpm): bump to 11.21.0
- chore(pnpm): move overrides and build settings to pnpm-workspace.yaml
- fix(create-itk-wasm): generate projects that install under pnpm 11
- chore(pnpm): bump pixi pnpm to 11 across the workspace
- chore(downsample): update js_package.py
- chore(transform-io): refresh vendored demo-app icons for shoelace 2.20.1
pnpm 11 no longer reads the "pnpm" field in package.json, and it replaced onlyBuiltDependencies with the allowBuilds map. Move the overrides into pnpm-workspace.yaml and fill in the allowBuilds placeholders that the 11.21.0 bump wrote out. The overrides had been inert since that bump, so the lockfile had fallen back to each package's own specifier. Regenerating it re-pins them, which collapses several duplicated dependency versions. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
pnpm 11 turned ignored build scripts from a warning into a fatal install error, so `pnpm install` in a generated project died with ERR_PNPM_IGNORED_BUILDS on protobufjs. Emit allowBuilds in the generated pnpm-workspace.yaml to allow the build scripts itk-wasm pulls in. Do not also list these under the pnpm 10 spelling, onlyBuiltDependencies: pnpm 11 weighs that key when deciding whether node_modules is stale but never writes it to .modules.yaml, so every install after the first sees a settings change and demands a modules purge. Underneath that sat a second failure that only surfaced once the first was fixed. A generated project is driven by two different pnpms: --build-and-test shells out to the system pnpm, while the pixi tasks used the pixi-provided pnpm 10. node_modules records the pnpm that wrote it, so the third install wanted to purge it and aborted with ERR_PNPM_ABORTED_REMOVE_MODULES_DIR_NO_TTY. Pin pixi to pnpm 11 so both agree, plus an explicit nodejs pin, without which the solver picks different node majors per platform. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The root pixi.toml was still on pnpm 10 and the package ones on pnpm 9, while package.json declares packageManager pnpm@11.21.0. That mismatch is not cosmetic: node_modules records the pnpm that wrote it, so alternating between the pixi-provided pnpm and the system one invalidated the modules directory on every switch, which aborts outright where there is no TTY. conda-forge's pnpm 11.21.0 requires nodejs >= 24.19, so the root nodejs pin moves from 22 to 24. This affects pixi tasks only; CI jobs get node from actions/setup-node and stay on 22. The package pixi.toml files pinned no nodejs at all, and letting the solver choose gave different node majors per platform (linux-aarch64 resolved 26.6.0 while linux-64 and osx-arm64 got 24.19.0), so pin the major there too. Regenerating the lockfiles rewrites them almost entirely; these environments had not been re-solved since the pnpm 9 era, so node 24 cascades through openssl, zlib, libuv and icu. `pixi update pnpm` produces the same churn as a full `pixi lock`. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
These Bootstrap Icons are vendored into the demo-app public assets by vite-plugin-static-copy. Refreshing them against @shoelace-style/shoelace 2.20.1 drops the now-redundant trailing closepath command from the path data and moves the icon LICENSE copyright to 2024. The directory is byte-identical to the installed dependency's dist/assets/icons. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Member
Author
|
CC @vboussot |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.