8000 Tags · blechschmidt/cloop · GitHub
[go: up one dir, main page]

Skip to content

Tags

Tags

v0.0.7

Toggle v0.0.7's commit message
v0.0.7

Built with Go 1.26.10 for crypto/x509's GO-2026-6809, with the security
fixes main has made since 0.0.6 — a git proxy that read a SHA-256
repository's ref delete as an update, dashboard model calls that ran an
agent on the hub's host on the hub's own Claude login, and resumed and
failed-over runs that acted on that login rather than their starter's —
and verified isolation claims, online rotation of the hub's CA, push
scanning, the model relay, firewall refusals and denial logs,
label-selector grants that deliver and sealing keys held in a KMS.
Executor protocol v26 against 0.0.6's v22. Sequence 1170 on main. Read
"Upgrading from 0.0.6" in CHANGELOG.md first: grants to a label selector
issued on an earlier build start delivering, so list them and revoke the
ones you did not mean to keep before upgrading.

v0.0.6

Toggle v0.0.6's commit message
v0.0.6

The security fixes main has made since 0.0.5 — GitHub credentials bound
to the forge host their grant is for, signature-verified project images
on edge devices and virtual executors, CLI cordon, drain and revoke that
take an edge device's credentials back, a push token out of the
harness's reach, API tokens minted without a role policy suspended, and
a root key that can be changed online and kept out of the environment —
with device forwarders for on-prem USB devices and network segments,
audit forwarding, an approvals inbox and task attachments, and executor
protocol v22 against 0.0.5's v21. Sequence 1116 on main. Read
"Upgrading from 0.0.5" in CHANGELOG.md first: the first start suspends
API tokens and removes Claude logins that 0.0.5 kept.

v0.0.5

Toggle v0.0.5's commit message
v0.0.5

The security fixes main has accumulated since 0.0.4 — among them a hub
without sign-in reachable from the network, web pages that could drive a
hub across sites and through DNS rebinding, stored XSS through a project's
name, unconfined project directories, revocations that never reached
running workloads and offboarding that left credentials behind — and
executor protocol v21 against 0.0.4's v13. The first release stamped with
its place on main (sequence 1082), so devices that run it are covered by
rollback protection. Read "Upgrading from 0.0.4" in CHANGELOG.md first.

edge

Toggle edge's commit message
fix(agent): an agent upgrades its own install, not the default one (T…

…ask 20376)

Found on sgx with a second agent installed beside the production one as
cloop-t20376: installTarget described the default install —
cloop-executor.service, /usr/local/bin/cloop — whichever agent asked. So the
second agent reported the production unit's helper as missing, and had it been
present would have filed its upgrade request into /var/lib/cloop-executor,
where the production helper would have upgrade
8000
d the production agent.

An agent now identifies its install from the kernel: the .service in its
/proc/self/cgroup, accepted only when that unit's ExecStart runs this very
binary (os.Executable, symlinks resolved) as `executor agent`. The state
directory, where the request is filed and the helper's path unit watches, is
the credential's directory. A process that merely shares a service's cgroup —
a test binary under the hub's own unit, an agent started from a service's shell
— is refused as unmanaged and never restarts that service. An init-script
install, which has no cgroup of its own, is found at the default path as
before.

`install` also prints the channel and the helper it set up.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

v0.0.4

Toggle v0.0.4's commit message
v0.0.4

The first published release of the executor installer fix 0.0.2 was cut for:
unversioned cloop_<os>_<arch>.tar.gz assets, each with its Sigstore bundle, so
the installer served at GET /install.sh and `cloop upgrade` can install from
releases/latest. 0.0.2 was tagged and never published (its upload failed), and
0.0.3's binaries did not build for linux/arm. See CHANGELOG.md.

v0.0.3

Toggle v0.0.3's commit message
v0.0.3

The first published release of the executor installer fix 0.0.2 was cut for:
unversioned cloop_<os>_<arch>.tar.gz assets, each with its Sigstore bundle, so
the installer served at GET /install.sh and `cloop upgrade` can install from
releases/latest. 0.0.2 was tagged and never published; its release job failed
while uploading. See CHANGELOG.md.

v0.0.2

Toggle v0.0.2's commit message
v0.0.2

Publishes the executor bootstrap installer fix that has been in the repository
since Task 20240 but never in a release.

v0.0.1 shipped versioned asset names (cloop_0.0.1_linux_amd64.tar.gz). The
installer at GET /install.sh fetches releases/latest/download/<fixed-name>,
which is the only URL that stays valid across releases — so it resolved
against nothing and every device got a 404. The repository was corrected four
days later; the release was not re-cut, so the breakage outlived its own fix.

This release publishes cloop_<os>_<arch>.tar.gz, adds linux/arm (armv7) for
Raspberry Pi-class edge devices, and signs every artifact with a Sigstore
bundle the installer verifies before unpacking anything as root.

v0.0.1

Toggle v0.0.1's commit message
cloop v0.0.1 — first tagged release

Everything in this release already existed; what is new is that it is
installable as a versioned binary rather than only from source.

Tagged at the first commit where all eight CI jobs pass. See CHANGELOG.md
for what is in it.
0