ci: push release tags one ref per push - #1100
Conversation
The repository ruleset rejects pushes updating more than 5 refs (GH013), so the 9-tag push at the end of the v0.9.0 run was refused wholesale — after every crate had already published. Push each created tag on its own instead of 'git push origin --tags' (which would also sweep up any unrelated local tags).
Deploying rmk-rs with
|
| Latest commit: |
a84fda2
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://d0f7dbac.rmk-4a2.pages.dev |
| Branch Preview URL: | https://fix-publish-tag-push.rmk-4a2.pages.dev |
Size Report
|
The resumed v0.9.0 Publish run (33238029609) got all nine crates onto crates.io, then died at
git push origin --tags: the repository ruleset rejects pushes that update more than 5 refs (GH013), so all 9 tags were refused atomically and the GitHub release was never created.Push each tag the run creates individually — immune to the ruleset limit and it no longer sweeps up unrelated local tags. After this merges, re-dispatching Publish skips all nine publishes (already on crates.io), creates and pushes the tags, and creates the
rmk-v0.9.0release (which fires the Discord announcement).