CHANGELOG: v1.1.0 !136
1 file changed, +42 −0
Layout: unified · split
CHANGELOG.org +42
| @@ -4,6 +4,48 @@ 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.1.0 — 2026-08-31 | ||
| 8 | |||
| 9 | Every release until now answered questions. This one notices something | ||
| 10 | on its own: that a repository's dependencies have moved, and says so | ||
| 11 | without being asked. | ||
| 12 | |||
| 13 | - Dependency update checks, opt-in per repository. A daemon worker reads | ||
| 14 | the manifests on the default branch, asks the ecosystem's registry what | ||
| 15 | the current release is, and maintains one issue per repository — opened | ||
| 16 | when something falls behind, rewritten when the set changes, closed once | ||
| 17 | nothing is behind. No package manager runs, so it needs no CI runner and | ||
| 18 | no configuration beyond turning it on. #58 | ||
| 19 | - =go.mod= against proxy.golang.org, =package.json= with | ||
| 20 | =package-lock.json= against npm, =Cargo.toml= with =Cargo.lock= | ||
| 21 | against crates.io, =requirements.txt= and =pyproject.toml= against | ||
| 22 | PyPI. A lockfile wins where both exist. A requirement naming a set | ||
| 23 | rather than a release — a range, a wildcard, a git or path source — is | ||
| 24 | skipped, since a range that already admits the newest release is not | ||
| 25 | news. | ||
| 26 | - =repo deps enable|disable|status=, a toggle on the repository settings | ||
| 27 | page, and the same three over the JSON API. | ||
| 28 | - Off by default, because checking a private repository tells a public | ||
| 29 | registry what it depends on. That is the owner's disclosure to make. | ||
| 30 | =[deps] check_interval_hours= sets the cadence, default 24. | ||
| 31 | - The issue is authored by a =gitbay-bot= account, so the existing | ||
| 32 | notification mail reaches the repository's owner rather than excluding | ||
| 33 | them as the actor. Its table is padded to its columns, which a | ||
| 34 | renderer ignores and a mail client needs. #61 | ||
| 35 | - =help= takes a prefix — =help mr= narrows the registry to one noun — and | ||
| 36 | every command now documents its arguments, so the server answers "what | ||
| 37 | are the flags" instead of being guessed at. #57 | ||
| 38 | - Web: settings rows end in one column of controls, checkboxes drawn at | ||
| 39 | the height of the inputs and buttons they sit beside #59; an added line | ||
| 40 | keeps its leading dash in the diff; a contributor's several verified | ||
| 41 | addresses collapse to one row #56. | ||
| 42 | |||
| 43 | Replace the binary and restart. Migration 0028 adds two tables and, when | ||
| 44 | the name is free, the =gitbay-bot= account. An instance already using that | ||
| 45 | name for a user or an org keeps what it has: the account is not created, | ||
| 46 | and dependency checks report that as the reason they cannot open an issue | ||
| 47 | rather than the migration failing and the daemon not starting. #64 | ||
| 48 | |||
| 7 | * v1.0.1 — 2026-08-30 | 49 | * v1.0.1 — 2026-08-30 |
| 8 | 50 | ||
| 9 | Two CI fixes found by running orgo's release pipeline on this instance. | 51 | Two CI fixes found by running orgo's release pipeline on this instance. |