Disclaimer: Found by an AI agent (Claude Fable 5) while porting this repo's release workflow for a Python generator; I'm filing on its behalf. Cosmetic, but verified against the workflow file and the published releases.
Summary
The Deployment Summary step in .github/workflows/release.yml prints Artifact: package.dhall, but the file the Create GitHub Release step actually attaches is ${{ steps.resolve.outputs.path }}, which is resolved.dhall. The published releases confirm it: the only asset on v0.7.1, v0.7.0 and v0.6.2 is resolved.dhall.
As of current master: files: ${{ steps.resolve.outputs.path }} at line 140, echo "Artifact: package.dhall" at line 151.
Expected
The summary names the real asset, resolved.dhall. One-word fix; happy to send a PR instead if that's easier.
Summary
The
Deployment Summarystep in.github/workflows/release.ymlprintsArtifact: package.dhall, but the file theCreate GitHub Releasestep actually attaches is${{ steps.resolve.outputs.path }}, which isresolved.dhall. The published releases confirm it: the only asset on v0.7.1, v0.7.0 and v0.6.2 isresolved.dhall.As of current master:
files: ${{ steps.resolve.outputs.path }}at line 140,echo "Artifact: package.dhall"at line 151.Expected
The summary names the real asset,
resolved.dhall. One-word fix; happy to send a PR instead if that's easier.