You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+16-1Lines changed: 16 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -80,6 +80,21 @@ cargo release --execute patch
80
80
cargo release --execute beta
81
81
```
82
82
83
+
### Release Flow Details
84
+
85
+
When you run `cargo release --execute <version>`, the following happens:
86
+
87
+
1.**cargo-release** creates a git tag and pushes it to GitHub
88
+
2.**GitHub Actions release workflow** triggers on the tag:
89
+
- Custom cargo-dist workflow creates a draft GitHub release
90
+
- cargo-dist builds artifacts for all platforms, uploads them to the draft release, and then publishes it
91
+
3.**post-announce workflow** runs:
92
+
- Updates the release title and body from the dist plan
93
+
- If it's a runner release (not pre-release): marks it as "latest" and triggers action repo workflow
94
+
- If it's a package release or pre-release: just updates the metadata
95
+
96
+
This ensures only stable runner releases are marked as "latest" in GitHub.
97
+
83
98
## Known issue
84
99
85
-
If one of the crates is currenlty in beta version, for example the runner is in beta version 4.4.2-beta.1, any alpha release will fail for the any crate, saying that only minor, major or patch releases is supported.
100
+
-If one of the crates is currenlty in beta version, for example the runner is in beta version 4.4.2-beta.1, any alpha release will fail for the any crate, saying that only minor, major or patch releases is supported.
0 commit comments