axodotdev / axodotdev/cargo-dist

GH workflow doesn't run when *more than 3* tags are pushed

Open
#190 9 comments 2 reactions 0 assignees View on GitHub
bug
Dominant language
Rust
Stars
2.1k
Forks
149
Avg merge
1d 11h
Merged PRs (30d)
32

Description

For proto (https://github.com/moonrepo/proto), we publish individual versions of each crate (using `cargo release`). This tags just fine, which you can see on the tags page: https://github.com/moonrepo/proto/tags

I've noticed this a few times now, that when I publish multiple tags, the GH dist/relase action does not run, resulting in no GH releases. On the tags page, notice that I just published `proto_cli-v0.1.7` alongside `proto_node-v0.1.3` and a few others, but no release was created.

I wouldn't be surprised if GH has some condition that these workflows only run for 1 tag...

Contributor guide

Open the contributing guide

Research direction

Start by inspecting the GitHub dist/release workflow and its tag-push trigger, then reproduce the case described with more than three crate tags, such as proto_cli-v0.1.7 and proto_node-v0.1.3. Done means the workflow runs for the multi-tag push and creates the expected GitHub releases.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, rust
Domain
ci-cd, release
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.