All notable changes to Brioche will be documented in this file.
Note that the individual Rust crates within this repo are not considered stable and changes will not be documented in the changelog.
Check the v0.1.6 announcement blog post for an overview of the new features in this release
- Add support for aarch64 Linux! We have been using a nightly build in the Brioche Packages repo for quite some time, so all existing packages are available for x86-64 Linux and aarch64 Linux (with a few exceptions due to upstream package limitations)
- Add new
brioche live-updatesubcommand. Projects can export aliveUpdaterecipe, which can update the project metadata, such as by bumping the version number based on an upstream repository. This feature mainly exists to automate package updates in Brioche Packages (#234) - Add
--no-verifyflag tobrioche publishto skip type-checking and validating a project when publishing. This can be useful e.g. in a CI pipeline if a package is checked in an earlier step (#326) - (Experimental): Add
--experimental-lazyflag tobrioche build. This will allow short-circuiting the build if the build result is already available in the remote cache. (This flag is experimental and could be either renamed or removed in the future!) (#294)
- Overhaul release and self-update process (#281)
- Support implicit dependencies via dynamic
import()calls (#356) - Support evaluating recipe exports that aren't functions (#357)
- Speed up
brioche checkwhen checking multiple projects (#255) - Speed up
brioche fmtwhen formatting multiple projects (#338) - Improve OpenTelemetry output (#305)
- Remove a few uses of the legacy registry API (#239)
- Fix "File exists" error that could sometimes happen when fetching a project from the registry (#259)
- Fix network errors not being retried when fetching from the cache (#286)
- Remove
brioche migrate-registry-to-cachecommand. This existed as an internal tool to help transition to the new cache, and so should no longer be needed (#355)
Check the blog post "Announcing Brioche v0.1.5" for an overview of the new features in this release
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
- 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.urlconfig key or the$BRIOCHE_CACHE_URLenv var can be used to cache with several different object storage backends. Check the documentation for more details
- Add support for unarchiving
.ziparchives (#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
unsandboxedsandbox backend (#230) - Add
process.currentDiroption to change which directory a process starts in (#231)
- Use
$BRIOCHE_DATA_DIRenv var to control where Brioche's data is stored-- in most cases, the default path is~/.local/share/briocheon Linux (#171) - Allow processes to inherit CA certificates from the host when the unsafe
networkingoption is enabled (#232)- In practice, this means that builds that access the network will no longer need to pull in the
ca_certificatespackage
- In practice, this means that builds that access the network will no longer need to pull in the
- Fix various issues with the LSP (#188)
- Tweak LSP to keep unused dependencies when saving (#192)
- Fix
brioche fmtwhen 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)
v0.1.4 - 2025-01-18
Check the blog post "Announcing Brioche v0.1.4" for an overview of all the new features in this release
- Overhaul console output (#137)
- The new output format uses colors and symbols, runs at a faster refresh rate, and generally should make it clearer what's going on. See this Asciinema recording for what the new format looks like.
- Overhaul output format when a process recipe fails (#138, #139)
- Add
--lockedflag for several subcommands (#133)- Applies to
build,check,run, andinstall. When passed, the command will fail if the lockfile isn't up-to-date.
- Applies to
- Add
--displayflag, plus newplain-reducedoutput format (#141) - Add new
attach_resourcesrecipe type (#149)
- Update Linux sandbox to fallback to using PRoot for mounts (#159)
- This fallback makes it so Brioche can run without any extra setup on Ubuntu 24.04-- although with reduced performance. See "PRoot fallback" in the docs for more context and other options.
- Fix some LSP errors from converting between line / column numbers and positions (#134)
- Add
project.brifor building Brioche with Brioche! This new build will be used to provide portable builds for non-glibc machines. - This release includes the initial groundwork for AArch64 support on Linux (a.k.a ARM64). Brioche itself can now run on
aarch64-linux, but this work hasn't landed in thebrioche-packagesrepo yet, and getting it merged so packages can work with bothaarch64-linuxandx86_64-linuxis still blocked on future feature work.
v0.1.3 - 2024-09-27
- Fix Brioche LSP erasing locked download and git ref hashes (#130)
- Fix "failed to move temporary project from registry" error. This occurred due to a race condition when a project tried to be fetched more than once from the registry, e.g. from a dependency shared by multiple other dependencies, like
std(#131) - Fix (very annoying!) "Request textDocument/diagnostic failed" error from LSP whenever a
.brifile was first opened (#132)
v0.1.2 - 2024-09-26
NOTE: These features require both the latest version of Brioche and an appropriate version of the
stdpackage. Consult the std changelog for more details
- Add
Brioche.download("..."). The provided URL will be downloaded, and the hash will automatically be recorded in thebrioche.locklockfile (#102) - Add
Brioche.gitRef({ repository, ref }). The git repository URL will be fetched, and the commit for the corresponding ref (branch or tag name) will be recorded in thebrioche.locklockfile. This is useful when used with thegitCheckoutfunction from thegitpackage (#126) - Add
std.glob(...)recipe. This takes a directory and some glob patterns, and returns a new directory containing only the contents matching a pattern. This is similar toBrioche.glob(...), but works with existing recipes instead of inputs from the project (#119)
- Fix
brioche self-updatecommand. Unfortunately, upgrading from v0.1.1 will still need to be done manually, but auto-updates should work going forward! (#112 by @jaudiger) - Fix
.unarchive()recipes sometimes not properly baking when unarchiving a tarfile containing long filename entries (#127, with work from #117 by @jaudiger
- Update most subcommands to take the
--project(-p) or--registry(-r) argument more than once. The command will apply to each project. This applies to the following subcommands: - Update
brioche fmtto print formatted files (#75 by @jaudiger) - Update
Process.dependenciesrecipes to support more flexible env var configurations. Namely, dependencies can now set env vars for fallbacks, in addition to the existing env vars that get appended
- Upgrade OpenTelemetry SDK packages. Brioche now uses the conventional OpenTelemetry SDK environment variables for configuration
- Upgrade Deno Core from v0.201.0 to v0.303.0
- Update Rust toolchain to v1.81
- Restructure some internal crates. Some crates that were originally in the main Brioche repository now live in
brioche-dev/brioche-runtime-utils
v0.1.1 - 2024-06-09
- Add new TypeScript runtime op to get the version of Brioche (#59). This will allow for updating packages to take advantage of new features without breaking backwards compatibility
- Add new
collect_referencesrecipe type (#57). This will be used by thestdpackage to improve container sizes
- Increase timeouts when fetching from registry from 10s to 120s (#54 by @matklad). This is a workaround due to very slow cold start times seen in some cases when making requests to the registry
- Tweak registry sync rules to avoid downloading unnecessary dependencies (#56). This should drastically reduce the download times during the first-time user experience (especially with some changes to the registry itself)
- Download project files in parallel from registry (#58)
v0.1.0 - 2024-06-02
- Initial release!