[renovate]

This PR contains the following updates:

Package	Update	Change
gastownhall/beads	patch	1.3.2 → 1.3.4

---

Release Notes

gastownhall/beads

v1.3.4

Compare Source

First stable release of the 1.3.4 patch line. It ships the same code as
[1.3.4-rc.1]; the only change since that candidate is the version stamp. The
full notes are in the [1.3.4-rc.1] section below. 1.3.4 is 1.3.3 plus one
fix: bd reads GT_ROOT from a rig's .beads/.env again.

There is no new migration file, and the embedded Dolt engine is
unchanged: upgrading from 1.3.x or 1.3.4-rc.1 is a binary swap.

Before promotion, 1.3.4-rc.1 passed gascity's RC Gate with bd pinned to the
candidate, on a throwaway branch off gascity's hotfix/1.5.1
(run 41791836358):

• It ran the same 155 jobs as the 1.3.3-rc.1 gate, and every job finished
  with the same result: 151 passing and 3 skipped.
• The one red job is an advisory probe that builds bd from main. That
  branch, like 1.3.3's, made two upstream-drift checks non-blocking.
• The gate does not demonstrate the fix: the 1.3.3-rc.1 gate ran bd without
  it and got the same results, and no job log in either run mentions
  GT_ROOT.

Upgrade notes

• Coming from 1.3.2 or earlier, read the [1.3.3-rc.1] Upgrade notes
  before upgrading. They still apply, except that GT_ROOT is no longer one
  of the .beads/.env keys bd ignores.
• The [1.3.3-rc.1] Known issues are not fixed in 1.3.4, whichever release
  you upgrade from. 1.3.4 does not include the #​7039 restore
  (#​8047), so do not run
  bd compact or bd flatten on a clone that adopted migration 0062 by
  bd dolt pull or bd bootstrap, or was cloned after it
  (#​7039).
• The 1.3.2 upgrade note still applies: run bd recompute-blocked once per
  workspace whose store crossed migration 0059 under bd 1.3.0 or later,
  which includes any workspace first created by bd 1.2.x or earlier
  (#​7037).
• Coming from 1.3.4-rc.1, nothing changes in behaviour.

v1.3.3

Compare Source

First stable release of the 1.3.3 patch line. It ships the same code as
[1.3.3-rc.1]; the only change since that candidate is the version stamp. The
full notes are in the [1.3.3-rc.1] section below, which covers everything
since [1.3.2]: security fixes, data-loss fixes and dependency updates, the
behaviour changes under Upgrade notes, and the Known issues that
1.3.3 does not fix, with their workarounds.

There is no new migration file, and the embedded Dolt engine is
unchanged: upgrading from 1.3.x or 1.3.3-rc.1 is a binary swap.

Before promotion, 1.3.3-rc.1 passed gascity's RC Gate with bd pinned to the
candidate: the same 155 jobs as the 1.3.2 gate, 151 passing and 3 skipped,
the remaining one being an advisory probe that builds bd from main. For
that run, two checks that track moving upstream heads, that probe and a
pack-pin check, were made non-blocking; both failed on upstream drift, not
on the candidate.

Upgrade notes

• Coming from 1.3.2 or earlier, read the [1.3.3-rc.1] Upgrade notes
  before upgrading. Several commands change what they accept or print:
  .beads/.env keys outside the allowlist are ignored with a warning,
  mail.delegate is read only from the environment and user config,
  option-shaped remote URLs are refused, bd rules compact needs --force
  to apply, and bd delete needs full ids.
• Read the [1.3.3-rc.1] Known issues, in particular the warning not to
  run bd compact or bd flatten on a clone that adopted migration 0062 by
  bd dolt pull or bd bootstrap, or was cloned after it
  (#​7039).
• The 1.3.2 upgrade note still applies: run bd recompute-blocked once per
  workspace whose store crossed migration 0059 under bd 1.3.0 or later,
  which includes any workspace first created by bd 1.2.x or earlier
  (#​7037).
• Coming from 1.3.3-rc.1, nothing changes in behaviour.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.