Repository navigation
Releases
1.3.7-alpha.1
- Smaller Borg UI image. The
borg-uisubmodule moves to a commit on top
of the v2.4.9 release that trims the UI image (karanhudia/borg-ui#1513): the
runtime base drops cron, gnupg, htop, ncdu, net-tools and tree and swaps
iotop for iotop-c, and Python's test and lint tools leave the image. The UI
image is about 170 MB smaller and has about a quarter fewer scanner findings.
A removed tool a hook script needs can come back from the Packages page
(sudo apt-get install …). Agent 0.1.24, no database change.
Full Changelog: 1.3.6...1.3.7-alpha.1
1.3.6
- Borg UI 2.4.9. The
borg-uisubmodule moves to the v2.4.9 release
(agent 0.1.24; one database migration, applied on startup).
What's Changed
- ci(deps): update github actions by @renovate[bot] in #141
- fix(images): update agent image by @renovate[bot] in #140
- release 1.3.6 with BorgUI 2.4.9 (upstream release v2.4.9; agent 0.1.24) by @ioanalytica in #143
Full Changelog: 1.3.5...1.3.6
1.3.6-rc.1
- Borg UI 2.4.9. The
borg-uisubmodule moves to the v2.4.9 release
(agent 0.1.24; one database migration, applied on startup).
What's Changed
- ci(deps): update github actions by @renovate[bot] in #141
- fix(images): update agent image by @renovate[bot] in #140
- release 1.3.6 with BorgUI 2.4.9 (upstream release v2.4.9; agent 0.1.24) by @ioanalytica in #143
Full Changelog: 1.3.5...1.3.6-rc.1
1.3.5
- Borg UI 2.4.8. The
borg-uisubmodule moves to the v2.4.8 release
(agent 0.1.23, no database change). - rclone 1.76.0 in the agent image. It fixes CVE-2026-111943 and
CVE-2026-78661. It refuses a redirect from HTTPS to HTTP, so a remote that
answers with one now fails: correct its endpoint inrclone.conf. The flag
--allow-https-downgradeis no substitute: many backends, S3, WebDAV and
Swift among them, refuse such a redirect anyway, and with the others
credentials and data would travel unencrypted. The Borg UI images keep
rclone 1.75.2 until Borg UI's runtime base moves.
What's Changed
- release 1.3.5 with BorgUI 2.4.8 (upstream release v2.4.8; agent 0.1.23) by @ioanalytica in #138
- build(agent): rclone 1.76.0, and accept the findings that wait on releases by @ioanalytica in #139
Full Changelog: 1.3.4...1.3.5
1.3.5-rc.2
- Borg UI 2.4.8. The
borg-uisubmodule moves to the v2.4.8 release
(agent 0.1.23, no database change). - rclone 1.76.0 in the agent image. It fixes CVE-2026-111943 and
CVE-2026-78661. It refuses a redirect from HTTPS to HTTP, so a remote that
answers with one now fails: correct its endpoint inrclone.conf. The flag
--allow-https-downgradeis no substitute: many backends, S3, WebDAV and
Swift among them, refuse such a redirect anyway, and with the others
credentials and data would travel unencrypted. The Borg UI images keep
rclone 1.75.2 until Borg UI's runtime base moves.
What's Changed
- build(agent): rclone 1.76.0, and accept the findings that wait on releases by @ioanalytica in #139
Full Changelog: 1.3.5-rc.1...1.3.5-rc.2
1.3.5-rc.1
- Borg UI 2.4.8. The
borg-uisubmodule moves to the v2.4.8 release
(agent 0.1.23, no database change).
What's Changed
- release 1.3.5 with BorgUI 2.4.8 (upstream release v2.4.8; agent 0.1.23) by @ioanalytica in #138
Full Changelog: 1.3.4...1.3.5-rc.1
1.3.4
- Borg UI 2.4.7. The
borg-uisubmodule moves to the v2.4.7 release
(agent 0.1.23, no database change).
Project and CI
- A release candidate is tagged on its release's commit.
X.Y.Z-rc.N
goes on the commit onmainwhoseChart.yamlsaysX.Y.Z, andX.Y.Z
on the same commit once the candidate passed, so a release is the source
its candidate tested andmainstays one line. Until now each candidate
was a commit of its own besidemain. The build gives the chart the tag's
version (scripts/chart-release-version.sh), a candidate shares the
CHANGELOG.mdentry of its release, andCONTRIBUTING.mddescribes the
steps of a release.
What's Changed
- ci(build): tag a release candidate on its release's commit by @ioanalytica in #136
- release 1.3.4 with BorgUI 2.4.7 (upstream release v2.4.7; agent 0.1.23) by @ioanalytica in #137
Full Changelog: 1.3.3...1.3.4
1.3.4-rc.1
- Borg UI 2.4.7. The
borg-uisubmodule moves to the v2.4.7 release
(agent 0.1.23, no database change).
Project and CI
- A release candidate is tagged on its release's commit.
X.Y.Z-rc.N
goes on the commit onmainwhoseChart.yamlsaysX.Y.Z, andX.Y.Z
on the same commit once the candidate passed, so a release is the source
its candidate tested andmainstays one line. Until now each candidate
was a commit of its own besidemain. The build gives the chart the tag's
version (scripts/chart-release-version.sh), a candidate shares the
CHANGELOG.mdentry of its release, andCONTRIBUTING.mddescribes the
steps of a release.
What's Changed
- ci(build): tag a release candidate on its release's commit by @ioanalytica in #136
- release 1.3.4 with BorgUI 2.4.7 (upstream release v2.4.7; agent 0.1.23) by @ioanalytica in #137
Full Changelog: 1.3.3...1.3.4-rc.1
1.3.3
- Borg UI 2.4.6, as in 1.3.2. The
borg-uisubmodule stays at the
v2.4.6 release (agent 0.1.22, no database change).
Project and CI
-
The daily CVE scan reports what matters.
.github/workflows/cve-scan.yml
also scans the third-party images the chart runs (busybox,
alpine/kubectl,redis) at the tagsvalues.yamlgives them, next to
ours atlatest(scripts/cve-scan-images.sh). Code scanning gets CRITICAL
and HIGH alone. The run fails, and a failed scheduled run is mailed, when an
image has a CRITICAL or HIGH that a newer package version fixes; its summary
lists them. Findings without a fix, and those with a fix k8s-borg cannot
install yet, which.github/cve-scan-accepted.yamllists with the reason
and an expiry date, show in code scanning only.
tests/cve-scan-workflow.batscovers the list, the gate and the summary. -
"Try it locally" runs against each tag's chart and images.
build.yml
calls.github/workflows/try-locally.ymlonce a tag's images and chart
are in GHCR, signed and tagged, with the tag as the version: the run pulls that
chart and installs it with the images it names, with the page and
examples/k3d/of the tag's commit. It stands beside the release, which
does not wait for it; a red run on an rc means the page or the release
needs a fix beforeX.Y.Zis tagged. A manual run takes a version as
well, to check a page change against a prerelease; the pull request run
and the weekly run are as before. Until now the page met a release's real
images only in the weekly run after the release: a release pull request's
run ends with a notice, and one that changes the page for the next
release fails against the published images (#122). -
A release's tags appear only once it is signed. A release pushed its
images and its chart under their tags and signed them by digest
afterwards, so a version was public and unsigned for minutes: Artifact Hub
indexed 1.3.2 in that time and does not check an indexed version again, so
it lists 1.3.2 as unsigned, andcosign verifyfailed for an image pulled
in between. The images and the chart now go up by digest alone (the chart
through a registry on the runner, ashelm pushtags what it pushes), the
sign job signs those digests, and a new job,tag, sets the tags after
it: the versions,sha-…, the shared Borg UI and runtime base tags,
latestfor a release, Artifact Hub's repository metadata and the chart's
version last. A failed signature leaves no tag behind, and a tag moves
only to the images of a later run: a late re-run of an older release's
failed jobs leaveslatestand the shared tags where a newer release put
them. The
server image builds on the runtime base by its digest, the chart job still
waits for the image builds, and "Try it locally" and the GitHub Release
wait for the tags.tests/release-signing.batskeeps the order (#133).
What's Changed
- ci(cve-scan): report CRITICAL and HIGH only, scan the chart's third-party images, fail on a fixable finding by @ioanalytica in #130
- ci(try-locally): run the page against the chart and images each tag publishes by @ioanalytica in #131
- ci(build): push the chart right before it is signed by @ioanalytica in #132
- ci(build): set a release's tags only after its digests are signed by @ioanalytica in #134
- release 1.3.3: tags only after signing (BorgUI 2.4.6 unchanged; agent 0.1.22) by @ioanalytica in #135
Full Changelog: 1.3.2...1.3.3
1.3.2
- Borg UI 2.4.6, as in 1.3.1. The
borg-uisubmodule stays at the
v2.4.6 release (agent 0.1.22, no database change).
Chart and images
-
A values schema. The chart carries
values.schema.json: Helm checks
the values of every install, upgrade, template and lint against it, and
Artifact Hub shows it as the chart's values reference, every parameter of
values.yamlwith its text and default. It refuses only what the chart
cannot use either: a mode other than the listed ones (node.backupMode,
cluster.mode,cluster.backupMode,s3.onMountFailure,
borgUI.redis.mode), a value of the wrong kind (text for a list, a list for
a switch, a fraction for a count) and aborgUI.errorReporting.enabled
that is no boolean. What a release sets in another form passes as before:
text as a number and numbers as text, as--set,--set-stringand Flux
valuesFromdeliver them, a switch as 0/1 or as text, a map or list empty
as the other kind ({},[],""). The schema does not change how the
chart reads a value: the text"false"still counts as on where a template
tests a switch. It requires no key and refuses no key it does not list, so
the chart's own message for the removedappandconfigsections stays,
and so do its checks behind the schema (helm --skip-schema-validation,
Helm 3.16 and later).tests/values-schema.batskeeps the schema in step
withvalues.yaml. -
Fewer known vulnerabilities in the images. The agent image ships
etcdctlandetcdutl3.6.16 (3.6.15), built with a Go release that fixes
the standard library CVEs of the old one, and no longer carries pip:
nothing in a container runs it, and each of its copies brought pip's known
CVEs and those of the setuptools code it vendors. The credentials
resolver's default image isalpine/kubectl:1.37.2(1.37.1), on a current
Alpine. Artifact Hub, which scans the chart's images, counted 79 known
vulnerabilities in the agent image of 1.3.1 and 70 in the kubectl image,
all of them with a fix; what stays in the agent image is msgpack, whose
version Borg pins, and the Go libraries of rclone and etcd that have no
fixed release yet.
What's Changed
- feat(chart): a values schema for Helm and Artifact Hub by @ioanalytica in #128
- release 1.3.2: fewer known vulnerabilities in the images (BorgUI 2.4.6 unchanged; agent 0.1.22) by @ioanalytica in #129
Full Changelog: 1.3.1...1.3.2