v1.5.2
Fixes
- Input contract: user-provided
contextanddockerfileinputs now correctly override the values derived fromservice_name/.skyhook/skyhook.yaml. Previously the resolve step always emittedresolved_context=code, which madeinputs.contextdead code (#5). - Drops
default: '.'anddefault: 'Dockerfile'from thecontext/dockerfileinputs (defaults still applied via build-step fallback) so the action can distinguish "user provided" from "user omitted". - Resolve step is gated on
service_name != '' && (context == '' || dockerfile == '')and only emitsresolved_*outputs when actually resolved from.skyhook/skyhook.yaml.
Behavior change
When service_name is provided but the config file or service is missing, the build now falls back to inputs.context || '.' instead of the implicit code/ safety net (commit 56d501c). The existing warning ("Falling back to input parameters") now matches behavior. Callers in this state should either fix their config or pass explicit context: code.
Precedence
inputs.X -> service_name-derived value -> default (. for context, Dockerfile for dockerfile).
Full Changelog: v1.5.1...v1.5.2