Repository navigation
fix: reduce PlatformClaw release image duplication - #382
Merged
Merged
Conversation
devSejung
force-pushed
the
fix/runtime-asset-dedup
branch
from
October 23, 2026 21:00
de910c8 to
f292364
Compare
devSejung
marked this pull request as ready for review
October 23, 2026 21:00
Contributor
Dependency graph guard clearedThis PR no longer has blocked dependency graph changes. A future dependency graph change requires a fresh
|
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
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.
What Problem This Solves
PlatformClaw ships duplicate Control UI assets and a full SkillHub JDK in its runtime images. The PR also needs to remain compatible with the current main branch and its security fixes.
Why This Change Was Made
User Impact
Less duplicated runtime content with the existing application paths and SkillHub behavior retained. The original packaging comparison measured 2,027,862,528 to 1,819,996,160 bytes in docker-save output (10.25%); that measurement predates the current main security update, and is not a new release-size measurement.
No configuration keys, defaults, required fields, or operator setup steps are added. The generated metadata's only semantic difference from current main is restoration of six existing Signal URL validators.
Evidence
Validation uses Docker Desktop Linux, Node 24.18.0, pnpm 11.15.1, and an init-backed task container. Production builds use NODE_ENV=production.
Exact pushed head
7081751f5ccb874e4696b5615a32a37795461959: GitHub CI run 40064039589 completed successfully. All 54 executed jobs passed; path-inapplicable jobs were skipped by the existing workflow. This includes production build artifacts, dependency/security gates, production and test typechecks, lint, configuration/SDK contracts, and all selected Node test shards. The PR is conflict-free against main4eb0fb51987827dea0b6344635d6a1506b4e51f9.