Commit a3366b0
committed
fix(ci): name rolling release packages after the branch, not the version number
The install page (<https://www.mrdocs.com/docs/mrdocs/install.html>)
reads the rolling-release assets via the GitHub API and picks one per
platform by filename suffix. Because each develop push named its
packages with the current project version (e.g.
MrDocs-0.8.0-Linux.tar.gz), a version bump produced a new filename and
left the previous version's files behind as stale assets on the
develop-release and master-release rolling releases. The first-match
lookup then happily returned the wrong (older) asset.
Thus, for non-tag publishes, rename each package from
MrDocs-<semver>-<platform>.<ext>
to
MrDocs-<ref-name>-<platform>.<ext>
right before the upload step. Subsequent pushes to the same branch now
produce identical filenames, which action-gh-release overwrites in
place. Tag releases, which are immutable per version, keep their
versioned filenames unchanged.
The upload glob is relaxed from `MrDocs-*.*.*-*.*` to `MrDocs-*-*.*` to
accommodate the branch-named form.
A one-time manual cleanup of legacy versioned assets on the existing
develop-release and master-release rolling releases is still required;
subsequent CI runs will keep the state clean on their own.1 parent 0246935 commit a3366b0
1 file changed
Lines changed: 22 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1082 | 1082 | | |
1083 | 1083 | | |
1084 | 1084 | | |
| 1085 | + | |
| 1086 | + | |
| 1087 | + | |
| 1088 | + | |
| 1089 | + | |
| 1090 | + | |
| 1091 | + | |
| 1092 | + | |
| 1093 | + | |
| 1094 | + | |
| 1095 | + | |
| 1096 | + | |
| 1097 | + | |
| 1098 | + | |
| 1099 | + | |
| 1100 | + | |
| 1101 | + | |
| 1102 | + | |
1085 | 1103 | | |
1086 | 1104 | | |
1087 | 1105 | | |
1088 | 1106 | | |
1089 | | - | |
| 1107 | + | |
| 1108 | + | |
| 1109 | + | |
| 1110 | + | |
1090 | 1111 | | |
1091 | 1112 | | |
1092 | 1113 | | |
| |||
0 commit comments