ci: fix publish dry-run failure states
Maintainers usually reply within 1 day
@smmckay is already working on this.
Since Nov 11, 2026.
Assessment
This issue has not been assessed yet.
Description
During the release of 0.7.0, we were bitten by the "Publish (Dry run)" step passing despite containing real errors; as a result, the actual "Publish" step failed, and a whole new 0.7.1 release had to be started after correcting the issue[^1]. Note that the "Publish (Dry run)" step runs as part of the "arch-independent checks" job, so we should have caught this weeks ago, but the "Publish (Dry run)" step isn't properly failing when errors occur.
Run with passing "Publish (Dry run)", failing "Publish": https://github.com/tailscale/tailscale-rs/actions/runs/42277910303/job/128110632629
Run from a PR a week ago with the same errors in "Publish (Dry run)": https://github.com/tailscale/tailscale-rs/actions/runs/41872805912/job/126724190632 (search for "no method named")
[^1]: The issue was that smoltcp failed to build without any feature flags enabled, as we had enabled the cubic congestion control feature for smoltcp by default, which in turn requires std. std is an optional feature for smoltcp, and publishing to crates.io requires crates to build without any features enabled, so the overall "Publish (Dry run)" and "Publish" steps failed. This is not the issue we want fixed; it should be fixed upstream in smoltcp's next release.
- Dominant language
- Rust
- Stars
- 1.2k
- Forks
- 75
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 22
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from tailscale/tailscale-rs
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
tailscale/tailscale-rs#485 ·
Maintainers usually reply within 1 day
-
documentation enhancement language support
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
tailscale/tailscale-rs#114 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
tailscale/tailscale-rs#39 ·
Maintainers usually reply within 1 day
-
Interest: kernel TUN overlay transport (acting as exit node / subnet router on small Linux routers)Open
Difficulty 5/5 Over a week Newbie friendliness 15/100
tailscale/tailscale-rs#486 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 57/100
tailscale/tailscale-rs#484 ·
Maintainers usually reply within 1 day
All issues in tailscale/tailscale-rs
Similar issues
-
bug UI
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
wardian-app/Wardian#1746 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
jlcodes99/cockpit-tools#3125 ·
Maintainers usually reply within 2 days
-
bug user-sprint
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Vondor/KassenSturz#967 ·
Maintainers usually reply within 1 day
-
area/ci
Difficulty 1/5 Under an hour Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
[BUG] Incremental sync warns "no stored highest_uid" on every round for folders with no new mailOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
rustmailer/bichon#411 ·