VERSION 0.7

[alexcb]

This is a high catch-all ticket for the upcoming VERSION 0.7 release.

The following features will be enabled by default:

• explicit-global
• check-duplicate-images
• earthly-version-arg
• use-cache-command
• use-host-command
• use-copy-link
• new-platform
• no-tar-build-output
• use-no-manifest-list
• use-chmod
• shell-out-anywhere
• use-registry-for-with-docker
• earthly-locally-arg
• use-project-secrets
• use-pipelines
• wait

The following feature(s) will remain as experimental, due to them (it) being too new:

• try

TODO:

• Draft release notes
• Finish up release notes (add information about all the breaking changes, expand on the meaning of each feature flag being flipped)
• Add docs for PIPELINE, TRIGGER, PROJECT, TRY (+FINALLY)
• Update docs to point to 0.7 in all examples update example version to 0.7 #2587
• Update docs for commands that are being GA'd in 0.7 to no longer say "beta" or "experimental"
• Edit existing secrets-related docs to update to the new secrets (+ add migration information)
• Finish Podman support, including necessary docs
• [Later] Update all syntax highlighting packages with the new commands: PIPELINE, TRIGGER, PROJECT, CACHE, WAIT, TRY, FINALLY.
• Remove --save-inline-cache and --use-inline-cache from --ci. They seem to be problematic in some cases and we don't know what the cause of this is (see e.g. buildkitd stuck at 100% CPU for 5 minutes during SAVE ARTIFACT for ~20 MiB output #1187)
• Force using the VERSION command at the top of every Earthfile (specifying VERSION 0.5 is still allowed, but it has to be explicit)
• use-copy-link changes WORKDIR when used with GIT CLONE #2544
• [Later] WAIT/END doesn't export to remote cache #2178
• unable to use ssh-ed25519 key: failed to create account: failed to create account: Internal #1783
• --use-copy-link breaks GIT CLONE #2272
• Images not output when mixing FROM +target and BUILD +target (on the same target) when --wait-block feature is used #2218
• rename output phases to summary #2609

Notes:

• We will do one or more v0.7-rc<n> release candidates prior to the full v0.7.0 release

[alexcb]

#2269 contains flags for docs

[alexcb]

we will aim to release WAIT in VERSION 0.7 too; however need to fix #2218 first

[r-LaForge]

The change of behaviour that comes with the --wait-block flag will fix a segfault encountered with --push and SAVE ARTIFACT in 0.6.

Edited: closes -> relates to
Relates to #2286

[alexcb]

The change of behaviour that comes with the --wait-block flag will fix a segfault encountered with --push and SAVE ARTIFACT.

Closes #2286

@r-LaForge We will still be supporting VERSION 0.6 once VERSION 0.7 is released (for at least a year, if not longer); ideally we'll want to fix the bug affecting 0.6 (however it'll be a lower priority since a work-around exists)

[rrjjvv]

Force using the VERSION command at the top of every Earthfile

Would this be for the Earthfile being directly invoked? Every Earthfile utilized in the build chain? Or some subset (e.g. IMPORT vs. target vs. UDC, remote vs. local, etc.)?

[alexcb]

Force using the VERSION command at the top of every Earthfile

Would this be for the Earthfile being directly invoked? Every Earthfile utilized in the build chain? Or some subset (e.g. IMPORT vs. target vs. UDC, remote vs. local, etc.)?

We were thinking every Earthfile; however just initially forcing it on the directly called Earthfile might be a more gentle nudge -- otherwise it makes importing remote UDCs (which one has no control over) impossible.

[rrjjvv]

otherwise it makes importing remote UDCs (which one has no control over) impossible

Exactly why I asked the question (e.g. earthly/lib#5, which is blocked by earthly/lib#7) 😄. Enforcing it for all Earthfiles referenced locally seems reasonable though (although there could still be edge cases like git submodules, where the Earthfile is 'local', yet still outside of your control... not sure how you can cleanly differentiate things like that).

[alexcb]

VERSION 0.7

should be equivalent to:

VERSION                             \
--check-duplicate-images            \
--ci-arg                            \
--earthly-git-author-args           \
--earthly-locally-arg               \
--earthly-version-arg               \
--explicit-global                   \
--git-commit-author-timestamp       \
--new-platform                      \
--no-tar-build-output               \
--shell-out-anywhere                \
--use-cache-command                 \
--use-chmod                         \
--use-copy-link                     \
--use-host-command                  \
--use-no-manifest-list              \
--use-pipelines                     \
--use-project-secrets               \
--wait-block                        \
0.6

The above can be helpful for pinpointing which feature leads to incompatabilities