Commit c96da98345
c96da983458654d7bc6d1abb79ad3e8e47bf5363
parent: dd2489b719
Unsigned ci/pages: success ci/test: success
cmc <hello@cleberg.net> · 2026-10-18 20:36 UTC
Remove the bot's ssh files before cargo publish (!13)
`cargo publish --locked` failed in build 53 (tag v0.24.1):
```
error: 3 files in the working directory contain changes that were not yet committed into git:
.bot_key
.known_hosts
.ssh_config
```
`.gitbay/bot-ssh.sh` writes them into the workspace, so the tree is dirty by the time `release.sh` reaches its last step. The release itself and all six tarballs were created and attached; only crates.io was missed. First release since bot-ssh.sh landed, which is why v0.24.0 was unaffected.
Deleted after the last ssh call, before publish.
Layout: unified · split
.gitbay/release.sh
+4
| @@ -57,6 +57,10 @@ for f in "$dist"/*; do |
| 57 | 57 | echo "attached $(basename "$f")" |
| 58 | 58 | done |
| 59 | 59 | |
| 60 | # bot-ssh.sh writes the bot's key and ssh config into the workspace, which leaves |
| 61 | # the tree dirty, and `cargo publish` refuses that. Nothing below here uses ssh. |
| 62 | rm -f .bot_key .known_hosts .ssh_config |
| 63 | |
| 60 | 64 | # --locked publishes exactly the dependency versions the tests ran against, |
| 61 | 65 | # rather than whatever resolves at publish time. |
| 62 | 66 | cargo publish --locked |