Skip to content

release: v1.0.0-rc.1 notes, changelog and pins - #76

Merged
jeefy merged 3 commits into
mainfrom
release/v1.0.0-rc.1
Oct 5, 2026
Merged

jeefy merged 3 commits into
mainfrom
release/v1.0.0-rc.1

Conversation

@jeefy

@jeefy jeefy commented Oct 5, 2026

Copy link
Copy Markdown
Owner

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-04 section, built from git 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 two ghcr.io/jeefy/booty:main docker-run examples pin :v1.0.0-rc.1, and a short Releases subsection under Quick start explains the tag scheme (CI-built vX.Y.Z with SLSA provenance and a keyless cosign signature, with the cosign verify-attestation one-liner from docker-publish.yml); :main keeps tracking the default branch, rc tags do not move :latest, CHANGELOG.md is the index.
  • examples/k8s.yaml: the Deployment image: and the BOOTY_IMAGE env 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_VERSION build-arg → main.version → /info.booty.version → About page), and the full changelog section.

Verification

  • go test ./... -race — clean.
  • cd web && npm run build — clean.
  • Dockerfile ARG BOOTY_VERSION ← workflow build-args: BOOTY_VERSION=${{ github.ref_name }} confirmed; AboutView.vue renders info.booty?.version.

Breaking changes (verbatim from CHANGELOG.md)

jeefy and others added 3 commits October 4, 2026 21:37
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>
@jeefy
jeefy merged commit 43ff41c into main Oct 5, 2026
5 checks passed
@jeefy
jeefy deleted the release/v1.0.0-rc.1 branch October 5, 2026 02:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant