Skip to content

Replace the misleading .claudeignore troubleshooting entry (#1843) #3634

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ayushcodes10 wants to merge 3 commits into
base: v8
Choose a base branch
from
Open

Replace the misleading .claudeignore troubleshooting entry (#1843) #3634

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
736b237
Replace the claudeignore troubleshooting entry with permissions deny
ayushcodes10 Sep 17, 2026
9367a08
Add changelog entry for issue 1843
ayushcodes10 Sep 17, 2026
2a39828
Merge upstream v8 into fix-1843-claudeignore-doc
ayushcodes10 Oct 10, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -323,6 +323,8 @@ Intra-class call binding across five languages, new language-structure coverage,

## 0.9.63 (2026-09-16)

- Fix: the README's prompt-cache troubleshooting entry told users to add `graph.json`/`graphify-out/` to a `.claudeignore` file — Claude Code never shipped `.claudeignore` support, so this was a no-op that left the symptom in place. Replaced with the supported `permissions.deny` rule in `.claude/settings.json`, plus a note that it trades off against the wiki-as-navigation workflow since a deny rule also blocks reading those files (#1843, thanks @chaosanderos).

- Feature: Elixir `alias`/`import`/`require`/`use` targets now resolve onto the module's `defmodule` node across files, so the internal module dependency graph is no longer dropped as dangling. Only top-level modules are indexed (a nested `defmodule`, labeled with its bare inner name, cannot capture an unrelated `use <Name>` from another file), and a same-file reference is left unresolved so it cannot clobber the structural `contains` edge (#3603, thanks @ayushcodes10).
- Feature: a Rust `self.method()` call now resolves to a method defined on the same type in another file (the common split-`impl`-block layout), pooling methods across every `impl` of one type and refusing to link when two unrelated types share a bare name (#3602, thanks @ayushcodes10).
- Feature: a Ruby member call `obj.foo` on a known-type receiver now resolves to a method `foo` inherited from a superclass, including across files, using the same conservative promotion as the implicit-self resolver — a single owning class, matching method kind, and one unambiguous ancestry chain, or it stays dangling (#3585, thanks @oleksii-tumanov).
Expand Down
Loading