Skip to content

fix(ci): use $name in archive template for multi-binary packaging - #12

Merged
seamoss merged 1 commit into
devfrom
fix/archive-template
Apr 24, 2026
Merged

seamoss merged 1 commit into
devfrom
fix/archive-template

Conversation

@seamoss

@seamoss seamoss commented Apr 24, 2026

Copy link
Copy Markdown
Owner

Summary

`taiki-e/upload-rust-binary-action` rejects `$bin` in the archive template when `bin:` lists multiple binaries — ambiguous naming. v0.4.0 shipped without tarballs for exactly this reason:

```
##[error]when multiple binary names are specified, default archive name or '$bin' variable cannot be used in 'archive' option
```

Swap to `$name` (Cargo.toml package name). Archives come out as `rat-rat-v0.4.0-.tar.gz`.

After merge

Trigger the workflow with `workflow_dispatch` + `release_tag=rat-v0.4.0` to retro-upload v0.4.0's four tarballs without needing a new release.

```sh
gh workflow run release-please.yml -f release_tag=rat-v0.4.0
```

taiki-e/upload-rust-binary-action refuses \`\$bin\` when the \`bin\` input
lists multiple binaries — it can't choose which one to name the combined
archive after. Replace with \`\$name\` (the Cargo.toml package name), so
the archives come out as \`rat-rat-v0.4.0-<target>.tar.gz\`.

Unblocks the v0.4.0 binaries (currently unattached) and any future
release. Use workflow_dispatch with \`release_tag=rat-v0.4.0\` after this
merges to retro-upload v0.4.0's tarballs.
@seamoss
seamoss merged commit 9c82a2d into dev Apr 24, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant