IW-346: Update release packaging for built artifacts #373
No reviewers
Labels
No labels
bug
contract
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
iterative-works/iw-cli!373
Loading…
Reference in a new issue
No description provided.
Delete branch "IW-346"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
build/iw-core.jar,build/iw-dashboard.jar) instead ofcore/**/*.scalasource files. Installed users no longer need Mill or any build infrastructure on their machine.iw-run) gets a documented three-tier order:$IW_*_JARenv override →$INSTALL_DIR/build/*.jar→ Mill (dev fallback).--bootstrapbecomes verify-only when bundled jars are present.iw-cli-cicontainer, withWEBAWESOME_NPM_TOKENwired through to drive Vite during dashboard packaging.commands/review-state.scalawas walkingcore/**/*.scalaat runtime; consolidated the dispatcher and three subscripts into one file that uses the standard--jar "$CORE_JAR"path. Net−70lines, no more runtime source walk, faster dispatch.millstub onPATHand asserts the launcher never invokes Mill when bundled jars are present.Phases
Review materials
Test plan
release/iw-cli-0.5.0.tar.gzv0.5.X-rc1orworkflow_dispatch) before any production release tag — required by Risk 1 mitigation inanalysis.md🤖 Generated with Claude Code