Orkuncakilkaya
d41de1f7c9
There was no release workflow. Artifacts were built by `x release --publish` on whatever machine the maintainer was sitting at, from whatever happened to be in bin/, with no checksums and nothing proving the tagged tree passed its tests. Pushing a v* tag now publishes. The workflow builds the toolchain from the IR seed, runs `x test`, `x test-tools` and `x bootstrap-cfree` against the tagged tree, and only then creates the Forgejo release. It refuses to publish when the tag and VERSION disagree, or when CHANGELOG.md has no section for that version. `x publish [vX.Y.Z]` is the command behind it and runs locally too. It builds dist/ — a source tarball from the tag, this host's toolchain, and a SHA256SUMS covering both — and takes the release notes from that version's CHANGELOG section, so notes and changelog cannot drift. It only adds assets the release is missing, which is how a macOS build gets attached to a Linux-built release. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| ai-seek-pathing.md | ||
| audio-link-windowed.md | ||
| become-anywhere.md | ||
| changelog-structure.md | ||
| char-escapes.md | ||
| clearcolor-expr.md | ||
| component-access.md | ||
| compound-assign-types.md | ||
| countdown.md | ||
| cursor-confine-mode3.md | ||
| diagnostics-file-line.md | ||
| duplicate-global-diagnostic.md | ||
| engine-enums.md | ||
| engine-ui-events.md | ||
| enum-typed-machines.md | ||
| fmt-paren-spacing.md | ||
| formatter-brackets.md | ||
| global-initializers.md | ||
| half-the-game.md | ||
| interp-braces.md | ||
| ivec2-members.md | ||
| key-constants-namespaces.md | ||
| layer-queries.md | ||
| less-to-write.md | ||
| list-literals.md | ||
| managers.md | ||
| namespace-named-args.md | ||
| os-pid.md | ||
| overlay-phase.md | ||
| prefabs.md | ||
| prefs-package.md | ||
| prelude-symbol-prefix.md | ||
| README.md | ||
| release-ci.md | ||
| reserved-word-functions.md | ||
| self-in-spawn-hooks.md | ||
| shooter-aim-centre.md | ||
| site-redesign.md | ||
| solids-solid2.md | ||
| sprite-atlas-ids.md | ||
| sprite-strip.md | ||
| tileskin-system.md | ||
| ui-close.md | ||
| ui-ids-anywhere.md | ||
| unary-minus-fixed.md | ||
Changesets
A changeset is one small Markdown file describing a single user-facing change,
dropped in this directory. x 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 (unlessx 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:
x release --dry-run