Orkuncakilkaya
44e752b606
The installer edited one profile — whichever ~/.zshrc or ~/.bashrc $SHELL pointed at — and skipped any profile that did not already exist. So a fresh account got nothing written at all, a bash user's ~/.bashrc is not read by the login shell macOS Terminal starts, and ~/.zshrc is only read by interactive zsh. The toolchain installed correctly and `ludic` was still not a command. The PATH edit now lives in one file, <install>/env (plus env.fish), and each profile gets a single line that sources it: ~/.profile for sh and for login bash with no .bash_profile, ~/.zshenv because zsh never reads ~/.profile and reads this one for every invocation, ~/.bashrc and ~/.bash_profile when they already exist, and fish's config when fish is installed. Missing .profile/.zshenv are created; .bash_profile deliberately is not, since creating it would stop bash from reading ~/.profile at all. Sourcing a shared file rather than appending an export keeps a re-install from accumulating a second entry, and leaves one place to delete when uninstalling. Verified with a staged HOME: zsh -i, zsh -c, bash -l, bash -i and sh -l all resolve ludic; a second run reports "already on your PATH" and writes nothing. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| README.md | ||
| version-from-install-root.md | ||
Changesets
A changeset is one small Markdown file describing a single user-facing change,
dropped in this directory. ludic dev release consumes every changeset here into a new
CHANGELOG.md section, bumps VERSION, and deletes the consumed files.
Format
bump: minor
type: feat
One or more lines describing the change, in the past-agnostic imperative used in
the changelog. Markdown is fine.
bump:—major,minor, orpatch(SemVer). The release version is bumped by the highest level among the pending changesets (unlessludic dev release <level>overrides it).type:— the Conventional Commit type (feat,fix,perf,docs, …). It decides which group the change lands in:feat→ Features,fix→ Fixes,perf→ Performance, and so on, in that order. A type with no known heading gets one named after itself.
Writing the body
The body is markdown and reaches the changelog as markdown: it becomes one list item, with continuation lines indented to stay inside it. Nested bullets, blank lines between paragraphs and inline code all survive.
bump: minor
type: feat
**Tiled map support** — load and draw Tiled maps.
- **TMX/TSX** — the XML formats, decoded to the same intermediate as JSON.
- **Collision** — the `collision` layer projects onto the engine tilemap.
Lead with the thing that changed, not with the mechanism. A reader scanning the release should be able to stop after your first clause.
Adding one
Create a file with a short, unique name, e.g. changes/regex-namespace.md. Any
filename works except this README.md, which the release step always skips.
Preview how the next release will read before cutting it — this writes nothing:
ludic dev release --dry-run