VERSION
command. The VERSION
command was first introduced under 0.5
and is optional as of 0.6
; however, it will become mandatory in a future version.VERSION
command. Consider a case where an Earthfile is developed against earthly v0.5.23
and makes use of the experimental FOOBAR
command, the first line of the Earthfile should be:0.X
), the FOOBAR
command might be promoted from the experimental stage to stable stage, at that point, version 0.X
would automatically set the --foobar
flag to true
, and the Earthfile could be updated to require version 0.X
(or later), and could be rewritten as VERSION 0.X
.--use-copy-include-patterns
--referenced-save-only
--for-in
FOR ... IN ...
commands--require-force-for-unsafe-saves
--force
for saving artifacts locally outside the Earthfile's directory--no-implicit-ignore
.earthlyignore
entries, such as Earthfile
and .tmp-earthly-out
--earthly-version-arg
EARTHLY_VERSION
and EARTHLY_BUILD_SHA
--shell-out-anywhere
ARG
)--use-copy-include-patterns
COPY
command. Without this feature, Earthly sends the entire directory of files excluding files listed in the .earthlyignore
file.--referenced-save-only
SAVE ARTIFACT ... AS LOCAL ...
and images resulting from SAVE IMAGE
and also execute RUN --push
commands only if they are connected to the main target through a chain of BUILD
commands.SAVE
BUILD -> SAVE
BUILD -> BUILD -> SAVE
BUILD -> BUILD -> BUILD -> SAVE
FROM -> SAVE
COPY -> SAVE
FROM -> BUILD -> SAVE
BUILD -> FROM -> SAVE
BUILD -> BUILD -> COPY -> SAVE
BUILD
commands, however the outputs will be subject to the following rules:SAVE ARTIFACT ... AS LOCAL ...
, with local Earthfiles will be outputSAVE ARTIFACT ... AS LOCAL ...
produced in remote targets will not be outputRUN --push
command will be executed if the target is remote--for-in
FOR ... IN ...
commandsFOR ... IN ...
commands.