This also means we cannot opt into bash (as opposed to sh) when installing dist itself (or cargo auditable, for that matter).
Part of #1509 become meaningful again (the whole GhaRunStep type) once we start doing some of the templating in dist itself.
It's also going to become a lot clearer what the CI pipeline is actually going to do, by just looking at the generated release.yml, rather than the actual steps being "hidden" in an artifact generated by plan.
We're running into GHA limitations: for example we cannot template
steps.0.shell
, see https://github.com/axodotdev/cargo-dist/pull/1509#discussion_r1831622985This also means we cannot opt into
bash
(as opposed tosh
) when installing dist itself (or cargo auditable, for that matter).Part of #1509 become meaningful again (the whole
GhaRunStep
type) once we start doing some of the templating in dist itself.It's also going to become a lot clearer what the CI pipeline is actually going to do, by just looking at the generated
release.yml
, rather than the actual steps being "hidden" in an artifact generated by plan.