Skip to content

chore(deps): bump chisel to v1.5.1 - #42

Merged
lczyk merged 2 commits into
mainfrom
chore/chisel-v1.5.1
Oct 8, 2026
Merged

lczyk merged 2 commits into
mainfrom
chore/chisel-v1.5.1

Conversation

@lczyk

@lczyk lczyk commented Oct 8, 2026

Copy link
Copy Markdown
Owner

bumps the chisel pin v1.5.0 -> v1.5.1.

upstream v1.5.1 = #325 (maintenance dates), #313 (current-archive fallback for recently-eol releases), #302 (trie path conflict check) and #290 (AGENTS.md only).

  • 0003 dropped -- it was our gated backport of #302, which is now upstream and ungated.
  • 0004 (perf: speed up path conflict detection聽letFunny/chisel#29, faster trie traversal) applies cleanly on v1.5.1's conflict.go, but with 0003 gone it would have run unconditionally. it now carries its own gate: newConflictTree sets a Fast flag from CHISEL_HACKS=1; unset = upstream's traversal (every child a candidate, fresh queues per path).
  • 0001 / 0002 unchanged, cmd_cut.go is byte-identical between the two tags.
  • contract test + release blurb updated to v1.5.1.

tested:

  • chisel go test ./... with patches applied, in ubuntu/go:1.25-26.04_edge: all green with and without CHISEL_HACKS=1. internal/setup 2.2s -> 0.9s with it set.
  • make binaries ARCH=arm64 ok; chisel-hacked --version -> v1.5.1-hacked.
  • bread-chisel-releases:{22.04,24.04,25.10,26.04,26.10}-arm64 built, chisel / chisel-hacked --version both report v1.5.1-hacked.
  • full spread suite not run locally (outer backend needs flock, macOS host) -- leaning on ci for that + amd64 / s390x / ppc64le.

lczyk added 2 commits October 8, 2026 15:27
v1.5.1 ships the trie path conflict check (canonical/chisel#302)
ungated, so the 0003 backport goes. 0004 (letFunny/chisel#29) now
applies straight onto upstream's conflict.go; it gets its own
CHISEL_HACKS=1 gate so unset keeps upstream's traversal.
@lczyk
lczyk merged commit f813719 into main Oct 8, 2026
9 checks passed
@lczyk
lczyk deleted the chore/chisel-v1.5.1 branch October 8, 2026 15:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant