Artifact fa54df559aa92c9a99253eefed2f0676c23891a97f1dd4d65914d20f18bfc8b1:
- File
bridge/go.mod
-
2026-05-04 19:11:34
— part of check-in
[c299ef11e2]
on branch chore/bump-libfossil-v0.5.0
— chore: bump libfossil → v0.5.0 in leaf and bridge modules
The auto-generated bump-upstream PR only updated the root module's go.mod. The leaf and bridge modules pin libfossil independently and need the bump too — without this, the upcoming #112 cleanup (delete ridToUUID + simplify Agent.Diff using libfossil v0.5.0's UUIDFromRID + whole-checkin Diff) can't land on leaf since leaf's go.mod still resolves to v0.4.5.
Worth fixing the bump-upstream workflow separately to walk every go.mod under the repo, but treating that as a follow-up rather than blocking this PR on it. (user: [email protected], size: 1864) [annotate] [blame] [check-ins using]
-
2026-05-04 19:17:25
— part of check-in
[c52b0b3b44]
on branch trunk
— chore: bump libfossil → v0.5.0 (#121)
* chore: bump libfossil → v0.5.0
* chore: bump libfossil → v0.5.0 in leaf and bridge modules
The auto-generated bump-upstream PR only updated the root module's go.mod. The leaf and bridge modules pin libfossil independently and need the bump too — without this, the upcoming #112 cleanup (delete ridToUUID + simplify Agent.Diff using libfossil v0.5.0's UUIDFromRID + whole-checkin Diff) can't land on leaf since leaf's go.mod still resolves to v0.4.5.
Worth fixing the bump-upstream workflow separately to walk every go.mod under the repo, but treating that as a follow-up rather than blocking this PR on it.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Dan Mestas <[email protected]> (user: [email protected], size: 1864) [annotate] [blame] [check-ins using]
-
2026-05-04 19:11:34
— part of check-in
[c299ef11e2]
on branch chore/bump-libfossil-v0.5.0
— chore: bump libfossil → v0.5.0 in leaf and bridge modules