Move L10-L20 line-range fix from 1.6.5 to Unreleased
v1.6.5 was tagged before the line-range fix landed; the fix is commit 23c26e1 on development and ships in 1.6.6+. Merge 21ce621 re-added the L10-L20 / L10 bullet under the already-cut 1.6.5 heading while resolving a CHANGELOG conflict; move it back to Unreleased so the changelog matches what the tag actually shipped. Co-Authored-By: siGit Code v1.6.5-acp <noreply@sigit.si>
Seto Elkahfi committed
Oct 9, 2026 at 09:49 UTC
3abd144dfb57b4e8dee91173a30c1df919f0de67
1 file changed
+9
-7
CHANGELOG.md
+9
-7
@@ -11,6 +11,15 @@
11
parsing the title, and a replayed thread from `session/load` carries the same
12
name (#196).
13
14
+### Fixed
15
+
16
+- **A linked selection written as `L10-L20` or `L10` reads just those lines.**
17
+ siGit Code read the line range of a `resource_link` only as `L10:20` or
18
+ `L10-20`, so `L10-L20` (the GitHub style) and a single line `L10` sent the
19
+ whole file instead of the selection. It now reads the same forms Zed's own
20
+ mention parser does, and a range that starts at line 0 or runs backwards
21
+ counts as no range.
22
+
23
## 1.6.5
24
25
### Added
@@ -46,13 +55,6 @@
55
56
### Fixed
57
49
-- **A linked selection written as `L10-L20` or `L10` reads just those lines.**
50
- siGit Code read the line range of a `resource_link` only as `L10:20` or
51
- `L10-20`, so `L10-L20` (the GitHub style) and a single line `L10` sent the
52
- whole file instead of the selection. It now reads the same forms Zed's own
53
- mention parser does, and a range that starts at line 0 or runs backwards
54
- counts as no range.
55
-
58
- **Tags a model makes up no longer show in the reply.** After a long run of
59
tool rounds, a model could start writing markup that looked like it came
60
from siGit Code: a `<system_warning>` block telling the user the previous