CHANGELOG: v1.2.1 !140
1 file changed, +14 −0
Layout: unified · split
CHANGELOG.org +14
| @@ -4,6 +4,20 @@ Versioning follows semver from v0.1.0. Database migrations run | |||
| 4 | automatically on daemon start; upgrade notes appear per release when | 4 | automatically on daemon start; upgrade notes appear per release when |
| 5 | anything beyond "replace the binary and restart" is needed. | 5 | anything beyond "replace the binary and restart" is needed. |
| 6 | 6 | ||
| 7 | * v1.2.1 — 2026-08-31 | ||
| 8 | |||
| 9 | Merging landed commits without running anything. | ||
| 10 | |||
| 11 | - A merge moves the target ref with a direct ref update, so it never | ||
| 12 | reached post-receive and none of the ref-update work fired: no =push= | ||
| 13 | event for webhooks to subscribe to, and no builds. Pushing a commit to a | ||
| 14 | branch ran the whole =.gitbay/ci.yml=; merging the identical commit ran | ||
| 15 | nothing. Both now happen in the merge path, with the build queueing | ||
| 16 | shared between it and post-receive rather than living in one of them. | ||
| 17 | #65 | ||
| 18 | |||
| 19 | Replace the binary and restart. | ||
| 20 | |||
| 7 | * v1.2.0 — 2026-08-31 | 21 | * v1.2.0 — 2026-08-31 |
| 8 | 22 | ||
| 9 | A merge request said what its state was and almost nothing about when it | 23 | A merge request said what its state was and almost nothing about when it |