Brioche Files

Check the blog post "Announcing Brioche v0.1.5" for an overview of all the new features in this release

Run brioche self-update to update an existing Brioche installation, or check the docs for installation instructions

Breaking

Note: This is a minor release, but Brioche is still pre-1.0 and not widely adopted, so we may ship minor breaking changes from time to time if we think the breakage will not affect many people

• (Minor breaking) The new caching system is replacing (most) uses of the Brioche registry. If you were syncing build artifacts to a custom registry before, you will need to migrate to a custom cache instead.
  • The registry is still used for resolving projects. For larger teams, it might still make sense to host a custom registry.
  • This release includes some minimal tooling to help migrate existing cached data from the old registry to a new cache, but it will be removed before the next release.
  • If you are self-hosting your own infrastructure for Brioche today (or are interested in doing so), please reach out for more information

Added

• Implement new caching system (#179)
  • Fetching from the official Brioche cache should be much faster in most cases
  • Using a private / self-hosted cache is much easier now. The cache.url config key or the $BRIOCHE_CACHE_URL env var can be used to cache with several different object storage backends. Check the documentation for more details
• Add support for unarchiving .zip archives (#176 by @paricbat)
• Add support for projects with cyclic imports (#211)
• Add command to start a debug shell within a failed build (#215)
• Add support for Brioche.gitCheckout() as a static (#218)
• Add unsandboxed sandbox backend (#230)
• Add process.currentDir option to change which directory a process starts in (#231)

Changed

• Use $BRIOCHE_DATA_DIR env var to control where Brioche's data is stored-- in most cases, the default path is ~/.local/share/brioche on Linux (#171)
• Allow processes to inherit CA certificates from the host when the unsafe networking option is enabled (#232)
  • In practice, this means that builds that access the network will no longer need to pull in the ca_certificates package

Fixed

• Fix various issues with the LSP (#188)
• Tweak LSP to keep unused dependencies when saving (#192)
• Fix brioche fmt when called without any args: it now defaults to formatting the project in the current directory (#190 by @asheliahut)
• Add missing implementations for several expressions when evaluating statics (#195)
• Fix potential segfault from V8 depending on CPU flags (#225)