# OSBuild - Build-Pipelines for Operating System Artifacts
## CHANGES WITH 9:
* The last pipeline stage is no longer automatically committed to the
store. This used to be a special case to make things work, but it has
now been properly fixed.
From now on, if you want a stage committed to the store, you need to
pass a `--checkpoint` option for the stage.
* The runner for the host system is now auto-detected. The
`runners/org.osbuild.default` symlink is now longer required (nor
supported).
* A generic runner named `org.osbuild.linux` was added. This runner
uses the default value of `ID` in `/etc/os-release`. That is, if the
local OS cannot be detected, or if no `os-release` file is provided,
this is the fallback runner that is used.
This runner only performs the bare minimum of initialization. It is
enough to run the most basic stages on all systems we tested.
* On Archlinux, the generic runner will now be used.
* A new runner for RHEL-8.1 is available.
* The JSON input to `osbuild` is now a monolithic manifest format which
contains all build information. For now, this means the input
manifest can contain a `pipeline:` key with the pipeline definition,
as well as a `sources:` key with external source definitions
previously passed via `--sources`.
The old input format is still supported, but will be dropped in the
next release.
* The osbuild sources now come with a man-page `osbuild(1)`. Further
pages will follow in the future.
Contributions from: Christian Kellner, David Rheinsberg, Jacob Kozol,
Lars Karlitski, Major Hayden, Martin Sehnoutka, Tom
Gundersen
- Berlin, 2020-03-05