Have workflows run dist plan on all known tags.

[duckinator]

General idea:

• add a command (or flag for dist plan) that prints a JSON representation of all possible tags
• in the generated workflow, use that new command to determine what tags there are, and run dist plan --output-format=json --tag=${TAG} > plan-dist-manifest-${TAG}.json for each one

Replaces #1560.

[ashleygwilliams]

i wonder if we shouldn't make this a tag command with the subcommand list, e.g. dist tag list

[duckinator]

As discussed on Discord, currently setting this aside because of the complexity caused by this:

cargo-dist/cargo-dist/templates/ci/github/release.yml.j2

Lines 143 to 149 in b487ee9

	dist
	{{%- if dispatch_releases %}} ${{ (inputs.tag && inputs.tag != 'dry-run' && format('host --steps=create --tag={0}', inputs.tag))
	{{%- elif release_branch %}} ${{ (!github.event.pull_request && 'host --steps=create --tag=timestamp --force-tag')
	{{%- else %}} ${{ (!github.event.pull_request && format('host --steps=create --tag={0}', github.ref_name))
	{{%- endif %}}
	{{%- if "axodotdev" in hosting_providers %}} || (env.AXO_RELEASES_TOKEN && 'host --steps=check') {{%- endif %}}
	{{{- " || 'plan' }} --output-format=json > plan-dist-manifest.json" | safe }}}

[alilleybrinker]

Hi @duckinator! Just to confirm, it sounds like from the last comment that the plan is to not resolve the dist plan issue with inconsistent tags in the immediate term. Do I have that right?

We're currently blocked on this for the next release of Hipcheck, and if that's the case we'll route around it. Of course we have the benefit of being able to fork and kludge our own thing in the meantime until this is resolved upstream.

[duckinator]

@alilleybrinker unfortunately the scope on this grew pretty significantly because of how much it interacts with other parts of the codebase. I ran into a thing blocking me from making any progress at all today, so I was asked to switch to a task I can actually make progress on. I'm not sure what the plan for this task is after today; I'd need to discuss that with @ashleygwilliams.

If you do try your own temporary fork and would like my input on something, I tend to be on the axodotdev Discord 10am-4pm eastern (7am-1pm pacific) on weekdays.

[alilleybrinker]

No problem! I'm talking with Ashley as well and will see what we can do. Thanks so much for the help so far on this, including the draft changes here! Totally understand about this hitting some complex parts of the system.

[duckinator]

We went with #1579 instead.