Commit db26399c9a

db26399c9aec29637d7b3338fde2b652c098802a

parent: 39dad8f75c

Verified · cmc ci/build: success ci/quality: success ci/test: success

cmc <hello@cleberg.net> · 2026-10-31 07:04 UTC

changelog: v1.46.0

Layout: unified · split

CHANGELOG.org +32
@@ -4,6 +4,38 @@ Versioning follows semver from v0.1.0. Database migrations run
44automatically on daemon start; upgrade notes appear per release when
55anything beyond "replace the binary and restart" is needed.
66
7* v1.46.0 — 2026-10-31
8
9Migrations 0080 and 0081. Every repository's pushes are secret-scanned
10in =warn= mode from this release on. Code scanning needs an image
11built from =deploy/Containerfile.security= and =[security] image= set;
12without them =repo security enable= refuses. The runner must be
13upgraded too for code scan results to be uploaded.
14
15- Dependency checks also match the resolved dependency set against OSV
16 and keep a second issue, "Known vulnerabilities in dependencies",
17 with the same lifecycle as the updates issue. Versions come from
18 =go.mod= (indirect requirements included), =package-lock.json=,
19 =Cargo.lock=, =uv.lock=, =poetry.lock= and SwiftPM's
20 =Package.resolved=, or exact pins where there is no lockfile. =repo
21 deps status= and the settings page list the matches (#338).
22- Pushes are scanned for credentials in self-identifying formats in
23 pre-receive. Findings name commit, path, line and rule, never the
24 value. =repo settings secret-scan <repo> off|warn|block= (default
25 =warn=: accepted, the pusher is told, the finding is audited as
26 =push.secrets=; =block= refuses, including a scan that failed),
27 =repo settings secret-scan-allow <repo> [<glob>...]= for paths whose
28 findings are ignored, and =repo secret-scan <repo>= over every ref
29 (#339).
30- Scheduled code scanning: =repo security enable|disable|run|status=
31 queue the instance's =gitbay-security= job from =[security]=
32 (=image=, =schedule=, =steps=). It gets no repository secrets and
33 sets no commit status. The runner uploads the SARIF its steps write
34 to =$GITBAY_RESULTS= with =runner results=, and gitbay-bot keeps a
35 "Code scanning findings" issue. The job name =gitbay-security= is
36 reserved in =ci.yml= (#340).
37- =golang.org/x/net= v0.62.0, =modernc.org/sqlite= v1.61.0; Go 1.27.3.
38
739* v1.45.1 — 2026-10-16
840
941No migrations.