Repository navigation
dev (rolling build of main)
Pre-releaseUnstable
This is the rolling build of main. It is rebuilt and replaced on every
push, and it is not a release: it reports the version of the last tag,
v0.112.1, with channel dev, and anything in it may change or break.
The numbered releases are the stable ones.
Built from commit d50d2d4a53ecf311b4a86f9cd5ebebeb5ca8dbd5 on 2026-10-21 14:44 UTC.
Since v0.112.1
Features
- chap-devops models disable --retire retires the model in chap-core
- Update says what changed in the marketplace registry
Documentation
- BUGS.md drops CLIM-1193, closed as covered by CLIM-1447
- BUGS.md names the Jira issues for the chap-core and timestamp bugs
Full changelog: v0.112.1...dev
Install
curl -fsSL https://raw.githubusercontent.com/winterop-com/chap-devops/main/install.sh | sh -s -- --version devOr into the current directory alone, as ./chap-devops, touching nothing else:
curl -fsSL https://raw.githubusercontent.com/winterop-com/chap-devops/main/install.sh | sh -s -- --version dev --hereA dev build follows this release from then on: chap-devops self update moves it
to the newest build of main, comparing commits rather than version
numbers, and chap-devops self version says channel dev. To go back to the
stable release:
chap-devops self update --version v0.112.1The Linux archives are static musl and run on any distribution, the macOS
archive is universal and is signed and notarized, and the Windows archives are
unsigned. Every archive holds the binary, README.md, LICENSE and shell
completions under completions/.
Verify
curl -fsSLO https://github.com/winterop-com/chap-devops/releases/download/dev/SHA256SUMS
shasum -a 256 -c SHA256SUMS --ignore-missingOn macOS, check the signature of the extracted binary:
codesign -dv --verbose=4 chap-devops