deps.env

# Pinned dependency versions for CI and Docker builds.
# See engdocs/archive/designs/image-dependency-versioning.md for the versioning
# strategy (archived, but still the only written record of it).
#
# Update these when bumping automation/image pins. The internal/deps package
# defines minimum compatible versions (may lag behind these pins).

DOLT_VERSION=2.1.7
BD_REPO=gastownhall/beads
# BD_VERSION is the installable default: a PUBLISHED beads release whose tarball
# SHA is pinned in .github/scripts/install-bd-archive.sh. Every required CI job
# downloads exactly this tarball, so it can only ever name a tag that has a
# GitHub Release with all four os/arch assets.
#
# It was held at v1.1.0 because no published release carried the conditional-write
# flags `--if-assignee`/`--if-status` (a rejected precondition is exit 13, nothing
# written, which is where the exit-13 constant comes from). That constraint is
# now lifted: v1.3.0 is cut from beads main well past 6e8af8bf8 (beads#5008,
# 2026-07-24) and 4b1d9c875 (beads#5364, 2026-08-05), and it publishes tarballs
# for all four os/arch tuples, so the ReleaseIfCurrent CAS contract now runs on
# the installable default rather than only on the source-built cell below.
BD_VERSION=v1.3.0
BR_VERSION=0.1.20

# Cross-version contract-test matrix pins.
# See engdocs/design/beads-gascity-contract-test-system.md.
# BD_PREV_VERSION is the minimum-supported bd: a published release whose tarball
# SHA is pinned in .github/scripts/install-bd-archive.sh (no API fallback on the
# required path). BD_CURRENT_VERSION is the bleeding-edge cell; the matrix builds
# it from beads source at BD_CURRENT_REF (a gastownhall/beads commit). Bump
# BD_CURRENT_REF deliberately, in lockstep with the vendored corpus, per the
# coordination protocol.
#
# The matrix axis is BD_PREV_VERSION vs BD_CURRENT_VERSION -- v1.0.4 against
# v1.3.0 -- and BD_VERSION is not a cell in it, so the installable default
# is free to sit anywhere at or above the floor without narrowing the axis.
# It sits on the current cell's own tag: BD_CURRENT_REF is the commit
# v1.3.0 is tagged at, so the installed tarball and the source build reach
# the same upstream commit by two different routes. That agreement is worth
# having -- it is what lets go.mod's library pin and the bd on PATH be the same
# beads, so gc cannot link one RC and shell out to another.
#
# BD_PREV_VERSION is also the floor that keeps BdStore's raw-SQL release fallback
# alive (bdSQLStringLiteral, releaseIfCurrentViaEmbeddedDoltSQL,
# parseDoltRowsAffected, isBdSQLUnsupportedInEmbeddedMode). Raising it past
# beads#5008 would delete all four, so it stays where it is: this bump is a pin
# move, not a support-floor decision.
BD_PREV_VERSION=v1.0.4
BD_CURRENT_VERSION=v1.3.0
BD_CURRENT_REF=f45b249ce6b40ba62aecc03949e6371e8f7c79d8