CHANGELOG: v1.3.0 !142
1 file changed, +18 −0
Layout: unified · split
CHANGELOG.org +18
| @@ -4,6 +4,24 @@ 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.3.0 — 2026-08-31 | ||
| 8 | |||
| 9 | A runner took every repository's work, which decided where you could run | ||
| 10 | one. | ||
| 11 | |||
| 12 | - =runner next= takes optional =owner/name= arguments and =gitbay-runner= | ||
| 13 | takes =-repos=, so a runner claims builds only for the repositories it | ||
| 14 | names. Naming none is the old behaviour, so an existing runner is | ||
| 15 | unaffected. This is what makes a runner outside the server practical: one | ||
| 16 | on a machine that should build a single project no longer picks up a | ||
| 17 | build belonging to someone else, which with open registration need not be | ||
| 18 | anyone the operator knows. The scoping is what the runner asks for rather | ||
| 19 | than an ACL the server holds over it — a runner account is admin by | ||
| 20 | necessity, so the boundary is the operator choosing how to start it. #66 | ||
| 21 | |||
| 22 | Replace the binary and restart. Runners want the new binary too, though an | ||
| 23 | old one keeps working unscoped. | ||
| 24 | |||
| 7 | * v1.2.1 — 2026-08-31 | 25 | * v1.2.1 — 2026-08-31 |
| 8 | 26 | ||
| 9 | Merging landed commits without running anything. | 27 | Merging landed commits without running anything. |