Repository navigation
release: v1.0.0-rc.1 notes, changelog and pins - #76
Merged
Merged
Conversation
Keep a Changelog format, newest first. The 1.0.0-rc.1 section is built from git log v0.3..main (330 conventional commits, 45 non-dependabot PRs), grouped as Breaking / Added / Fixed / Security / Documentation, written for a homelab operator rather than as a commit dump. Older releases collapse to a single line that links the GitHub release page; reconstructing them is out of scope. Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-openagent) Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
… note Replace the :main pins in the README's two docker run examples and in examples/k8s.yaml (Deployment image and BOOTY_IMAGE env) with :v1.0.0-rc.1 so an operator following the docs installs the release candidate, not a moving branch tip. Add a short Releases subsection under Quick start: vX.Y.Z tags are built by CI with SLSA provenance and a keyless cosign signature (with the cosign verify-attestation one-liner from the workflow), :main tracks the default branch, rc tags do not move :latest, and CHANGELOG.md holds the notable changes between releases. Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-openagent) Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
Headline paragraph (PXE/HTTP-boot server that now also bootstraps the cluster and runs self-healing OS upgrades; proven on a 5-node homelab of Bluefin Server and Flatcar hosts), an Upgrading-from-v0.3 section covering the automatic data-dir migration, the removed/deprecated flags, the new examples/k8s.yaml ClusterRole and the POD_NAMESPACE/BOOTY_IMAGE env vars with a kured recommendation, the rc known-limitations list (WoL untested live, SSH actuator unit-tested only, no auth by design, Bluefin GPU needs >= 26.10.862, NFSv3 on Bluefin blocked upstream), a note on the BOOTY_VERSION tag -> /info.booty.version -> About page plumbing, and the full 1.0.0-rc.1 changelog section. Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-openagent) Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prepares the first release since v0.3 (2023-12-21) to be tagged v1.0.0-rc.1. Does not tag or publish; that happens after this lands.
What is in here
CHANGELOG.md(new, Keep a Changelog style): the## [1.0.0-rc.1] - 2026-10-04section, built fromgit log v0.3..main(330 conventional commits across 45 PRs), grouped as Breaking changes / Added / Fixed / Security / Documentation and written for a homelab operator, not as a commit dump. Older releases collapse to a one-line link to the GitHub release page.README.md: the twoghcr.io/jeefy/booty:maindocker-run examples pin:v1.0.0-rc.1, and a short Releases subsection under Quick start explains the tag scheme (CI-builtvX.Y.Zwith SLSA provenance and a keyless cosign signature, with thecosign verify-attestationone-liner fromdocker-publish.yml);:mainkeeps tracking the default branch, rc tags do not move:latest,CHANGELOG.mdis the index.examples/k8s.yaml: the Deploymentimage:and theBOOTY_IMAGEenv pin:v1.0.0-rc.1(the two must stay equal).docs/releases/v1.0.0-rc.1.md: the release notes draft for the GitHub release page — headline paragraph, "Upgrading from v0.3", known limitations for the rc, a note on the version plumbing (BOOTY_VERSIONbuild-arg →main.version→/info.booty.version→ About page), and the full changelog section.Verification
go test ./... -race— clean.cd web && npm run build— clean.DockerfileARGBOOTY_VERSION← workflowbuild-args: BOOTY_VERSION=${{ github.ref_name }}confirmed;AboutView.vuerendersinfo.booty?.version.Breaking changes (verbatim from CHANGELOG.md)
ostreeImageintodata/registry/is gone, together with the/registryand/v2/endpoints and the UI's Cache page. Hosts rebase straight from their own registry, exactly what{{ .OSTreeImage }}renders.--ociGCand--ociGCEmptyare accepted as deprecated no-ops so an old command line still starts, and go away in the next release. On start-up an emptydata/registry/is removed silently; one that still holds blobs is left in place with a warning. (Storage view, --coreOSChannel=none, and the OCI image cache removed #73)data/<os>/<version>/. Flatcar, CoreOS and Bluefin now keep each release underdata/<os>/<version>/behind relativecurrent,previousandlastGoodsymlinks. Booty migrates older layouts automatically on start-up; the pre-migration top-level names (data/flatcar_production_pxe.vmlinuz,data/fedora-coreos-<version>-live-*) stay as symlinks into<os>/current, so anything that still references them keeps working. (Autopilot P1: health reports, release retention and per-host targetVersion #40)coreuser;rootis locked by the image. Upstream Bluefin Server 26.10 (fix(security): ship root locked; provision access per node projectbluefin/server#275) ships root locked and runs sshd without PAM, so the previous "put keys on root" behaviour is unusable. Booty now provisionscorewith your--sshAuthorizedKeys, passwordless sudo andsshd.serviceenabled. SSH ascore, notroot. (fix(bluefin): SSH as core; root is locked by the image since 26.10 #70)/update-checkon Bluefin answersrebootRequiredfrom the target rule. The rule is the same for every OS now:rebootRequiredwhen the host's effective target (itstargetVersionwhen set, else the fleet target) differs from what it reports running. A diskless Bluefin host behind its target is told to reboot and re-image. (Autopilot P1: health reports, release retention and per-host targetVersion #40)--builtindefault gainshealthandwol. The default value is nowhostname,update,booted,sshkeys,health,wol. Hosts pick up two new systemd units on next boot:booty-health.servicePOSTs a health report to/healthaftermulti-user.target, and10-booty-wol.linkarms Wake-on-LAN on the host's NIC. Pass--builtin=hostname,update,booted,sshkeys(ornone) to opt out. (Autopilot P1: health reports, release retention and per-host targetVersion #40, Power: per-host state, Wake-on-LAN, reboot and shutdown #67)GET /clusteraddssource/connected/nodes/apiServer, andreadymeans "connected" in external mode. In the default--controlPlane=externalthere is no bootstrap to wait for, soreadyreports whether Booty can talk to the API server;readyAtis omitted. In managed mode the meaning is unchanged (kubeadm initfinished,/readyzanswers). (fix(cluster): GET /cluster and the Cluster card reflect an external control plane #64)--rebootSSHKey, else a privileged reboot Pod from Booty's own image as the last resort. An explicit SSH key now wins over the API actuator, which matches the operator intent of handing Booty a key. Operator Power buttons never go through kured. (fix(autopilot): prefer --rebootSSHKey over the API reboot Pod #65, Power: per-host state, Wake-on-LAN, reboot and shutdown #67)--coreOSChannel=noneand--flatcarChannel=noneare now real opt-outs. Setting a channel tononestops version checks and downloads for that OS, answers/update-checkand/infoas if no release were cached, refuses new registrations of it with400, and serves an already registered host a refusal menu. The directory is left on disk and listed by/storageastracked:falseuntil you delete it by hand. (Storage view, --coreOSChannel=none, and the OCI image cache removed #73)GET /autopilotis bounded by default. The answer now carries the newest 10goodrecords whose files were pruned (plus every live record) and the newest 100 of the 200-event ring;releaseCountandeventCountsay what was left out. Use?releases=alland?events=allfor the whole history. (Bound the autopilot's release history, GET /autopilot and the Autopilot page #75)