History

Orkuncakilkaya bfa763a55b fix(install): cover a non-login interactive bash ~/.bashrc was only appended to when it already existed, so on an account without one — a fresh container, a minimal image — `bash -i`, which is what most Linux terminal emulators start, did not see the toolchain even though every other shell did. .bashrc is now created when missing. Unlike .bash_profile, whose existence stops bash reading ~/.profile, a .bashrc that only sources the env file changes nothing else about how bash starts. Verified across zsh -i, zsh -c, bash -l, bash -i, sh -l and dash -l on a staged HOME: all six resolve ludic, a second run writes nothing, and .bash_profile is still never created. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-05 22:33:35 +03:00
..
bashrc-noninteractive.md	fix(install): cover a non-login interactive bash	2026-09-05 22:33:35 +03:00
README.md	feat(cli): install in one command, and call the CLI `ludic`	2026-09-05 22:01:52 +03:00

Orkuncakilkaya bfa763a55b fix(install): cover a non-login interactive bash

~/.bashrc was only appended to when it already existed, so on an account without
one — a fresh container, a minimal image — `bash -i`, which is what most Linux
terminal emulators start, did not see the toolchain even though every other
shell did.

.bashrc is now created when missing. Unlike .bash_profile, whose existence stops
bash reading ~/.profile, a .bashrc that only sources the env file changes nothing
else about how bash starts.

Verified across zsh -i, zsh -c, bash -l, bash -i, sh -l and dash -l on a staged
HOME: all six resolve ludic, a second run writes nothing, and .bash_profile is
still never created.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-09-05 22:33:35 +03:00

bashrc-noninteractive.md fix(install): cover a non-login interactive bash 2026-09-05 22:33:35 +03:00

README.md feat(cli): install in one command, and call the CLI ludic 2026-09-05 22:01:52 +03:00

README.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, or patch (SemVer). The release version is bumped by the highest level among the pending changesets (unless ludic 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