0.7

bits 0.7

The full changelog is in the CHANGELOG.

Highlights

• Scheduled builds, CI on push and publishing from bits-console. A slot builds a package on its platforms. It can do so nightly, on each commit to the branches it follows (build only, or build and publish), or by publishing the latest version to its final destination, for example views/current following main. See WORKFLOWS, Phase 4, and Step 6 for publishing to the final destination.
• A build plan before every build. It shows where each package comes from and why one is rebuilt. Build-only dependencies of reused packages are no longer fetched or built. See Previewing a build.
• Several binary stores, and a store cache for recipes' own downloads. See Sharing binaries through a store and Remote binary store backends.
• bits outside CERN. CERN's defaults moved into site configuration files, which another site can replace. See Site configuration.
• Simpler environments. bits use --architecture x86_64-el9 --defaults gcc14::opt saves the platform and the defaults. From them bits q, bits enter and bits clean find the right build. They also work without a work directory, from a community's modules on CVMFS. See Configuration and Managing environments.
• CVMFS publishing. bits cvmfs release --pipeline makes a release and its view from one build, at any time. Releases replace only what another build published. A merged view's setup.sh sets up what its modules do. See bits store / bits cvmfs.
• SBOMs and vulnerabilities. Recipes can name CPEs and purls, and system packages are recorded with their versions. bits-console scans published builds, triages findings and analyses licences, and makes upgrade plans that bits upgrade applies. See bits upgrade and bits sbom.
• Help chat in bits-console and its phone app. It answers from the docs, and explains failed builds from what the service recorded of them.
• Documentation. Find what you need lists common tasks with links, and the FAQ is grouped by what you are doing.