Skip to content

Release 0.1.0 - #28

Merged
dtt-github merged 1 commit into
mainfrom
release-0.1.0
Nov 6, 2026
Merged

dtt-github merged 1 commit into
mainfrom
release-0.1.0

Conversation

@dtt-github

Copy link
Copy Markdown
Owner

Step 4 of the plan, and the last one: release 0.1.0.

What this changes

  • CHANGELOG. The Unreleased section becomes 0.1.0 (2026-11-06).
    • It opens with a short summary of the release, linking to the release rehearsal and to the README's what works, and what doesn't yet.
    • The older notes, written before the changelog was kept, are renamed to "Before 0.1.0", so 0.1.0 appears only once.
    • Version links are added at the bottom.
  • Version numbers. Already 0.1.0 in the Rust workspace and the web app, so nothing to change.

After merge

  1. Tag main as v0.1.0.
  2. Publish a GitHub release with short notes that link to the CHANGELOG.

There's no server deployment.

The release checks from the plan:

  • The counter, UART receiver and FIFO starters reach a clean layout with no code typed by hand (#26).
  • Health shows every case tried and every planted mistake caught for those three (#25, #26).
  • A clean clone runs by following Getting started (#27).
  • CI is green, and the docs and CHANGELOG match what ships (this PR).

🤖 Generated with Claude Code

The CHANGELOG's Unreleased section becomes 0.1.0 (2026-11-06), with a
short summary of what the release does and links to the rehearsal and
the README's limits; the notes from before the changelog was kept are
renamed so 0.1.0 appears once. Version numbers are already 0.1.0.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@dtt-github
dtt-github merged commit d6d0830 into main Nov 6, 2026
2 checks passed
@dtt-github
dtt-github deleted the release-0.1.0 branch November 6, 2026 21:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant