Resolve prebuilt assets from the selected module
This commit is contained in:
@@ -99,7 +99,14 @@ later partial-artifact behavior intact.
|
||||
|
||||
## Issue 3: Use the module path base for relative prebuilt assets (P2)
|
||||
|
||||
Status: open. Category: incomplete module path adoption.
|
||||
Status: complete. Category: incomplete module path adoption.
|
||||
|
||||
**Completion:** Build output and CLI prebuilt assets share the selected module's
|
||||
directory resolver. CLI and pending migration guidance describe the common base.
|
||||
Local hosted regression tests verify root and nested relative build/delivery
|
||||
pairs, absolute output, module binding, and rejection of changed artifact content
|
||||
before hosted requests. Existing receipt/content checks and nested build cases
|
||||
pass offline.
|
||||
|
||||
**Evidence:** [CLI prebuilt delivery](../../cmd/releasekit/main.go) joins a
|
||||
relative `--assets` directory to `invocation.Repository`. Builds now resolve
|
||||
|
||||
Reference in New Issue
Block a user