docs(install): warn about multiple distribution channels (#314)#320
Merged
Conversation
The install docs listed several methods without warning that having more\nthan one on $PATH silently resolves to whichever appears first. On a real\ndeveloper machine three copies were present simultaneously\n(~/.local/bin, ~/.cargo/bin, ~/.bun/bin) and the stale npm v0.2.4 was\nbeing invoked, causing confusing behavior.\n\nChanges\n- README: pick one recommended method, list all supported channels in a\n table, and add a `which -a cora && cora --version` check snippet with\n guidance for pruning stale copies.\n- Cross-link issue #314 for background.\n- CHANGELOG entry under ## [0.6.1] -> Changed — Docs.\n\nAlso closes #315 as a duplicate of #314 (same title/body/author, opened\n3 seconds apart).\n\nBump 0.6.0 -> 0.6.1 (patch; docs only).
8a70b0a to
25ea336
Compare
This was referenced Jun 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #314 — install instructions don't warn about multiple distribution channels causing PATH conflicts.
The install docs listed several methods (installer script,
cargo, pre-built binaries, npm) without warning that having more than one on$PATHsilently resolves to whichever appears first. On a real developer machine three copies were present simultaneously (~/.local/bin/cora,~/.cargo/bin/cora,~/.bun/bin/cora) and the stale npm v0.2.4 was being invoked, causing confusing behavior with no warning.Closes #315 as a duplicate of #314 (same title, body, author, opened 3 seconds apart — already closed on the issue tracker).
Changes
README.md— Install sectioncargo/ pre-built binaries).corayou're running" snippet usingwhich -a cora(lists everycoraonPATH) andcora --version.PATH).CHANGELOG.mdEntry under
## [0.6.1] -> Changed — Docs.Tests
Docs-only change.
cargo buildandcargo fmt --checkstill pass to keep the version bump consistent with the rest of the 0.6.1 patch bundle.Versioning
Patch bump
0.6.0→0.6.1(shares the release with #316, #312, #313).Cargo.tomlwill conflict with #317, #318, and #319. Suggested merge order: #317 → #318 → #319 → this PR (docs last). Conflicts are confined to the## [0.6.1]block ofCHANGELOG.mdand the version line inCargo.toml/Cargo.lock.Checklist
cargo buildpassescargo fmt --checkclean## [0.6.1]→### Changed — DocsCargo.toml+Cargo.lock