From 7d42469f5fb70191e3e733c3feb4abae39ccf500 Mon Sep 17 00:00:00 2001 From: Anastassios Nanos Date: Sat, 31 Oct 2026 14:47:27 +0200 Subject: [PATCH] fix(bundle): Carry brig v0.5.0 A direct install from this repository's install.sh gets the brig the bundle carries, and v0.1.0-rc19 carries brig v0.4.1. brig v0.5.0 is released, and its archive carries brig-broker, so the bundle now packages the broker as well and a route can start on a direct install. brig's own install.sh replaces the bundle's brig with the release it installs, so only the direct path is behind. Signed-off-by: Anastassios Nanos --- scripts/build-bundle.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/build-bundle.sh b/scripts/build-bundle.sh index 1bb2c21..d25eedb 100755 --- a/scripts/build-bundle.sh +++ b/scripts/build-bundle.sh @@ -95,7 +95,7 @@ done # The brig release this bundle carries. On Linux it is the brig a user gets, # so it is pinned like every other component. Bump it with the brig release a # bundle is cut for. BRIG_VERSION=latest still works for a local build. -BRIG_VERSION="${BRIG_VERSION:-v0.4.1}" +BRIG_VERSION="${BRIG_VERSION:-v0.5.0}" BRIG_REPO="${BRIG_REPO:-brig-sh/brig}" # urunc has no release that carries what brig needs, so it is built from # source, and the source is pinned to one commit. A branch tip