Skip to content

Prepare the 0.2.0 release - #7

Merged
iharhl merged 1 commit into
mainfrom
release-prep/v0.2.0
Nov 8, 2026
Merged

iharhl merged 1 commit into
mainfrom
release-prep/v0.2.0

Conversation

@iharhl

@iharhl iharhl commented Nov 8, 2026

Copy link
Copy Markdown
Owner

Release prep for v0.2.0: version bump, a README that covers from-elf from the start, and the release strategy in RELEASING.md.

Changes

  • Version 0.2.0 in pyproject.toml, uv.lock and memmap/__init__.py. uv version --bump does not touch __version__, so test_version_matches_pyproject in tests/test_cli.py now fails when the two differ.
  • README
    • The intro names both ways to get a config: write the YAML by hand, or generate it from a linked ELF with from-elf.
    • One quick start with two starting points, both leading to check → describe → render.
    • Separate "Writing a config" and "Generating a config from firmware" sections, then the commands table.
    • Commands are written as memmap ..., with one note to add uv run from a checkout.
    • Shows how to install the raster extra from a release URL.
  • RELEASING.md
    • Releases are cut from main through a short-lived release-prep/vX.Y.Z branch and a PR.
    • The tag goes on the merged commit on main.
    • A release/X.Y branch is only for fixing an older version.

For reviewers

  • The "memmap[raster] @ <wheel URL>" install form was checked against a locally built 0.2.0 wheel with uv pip install --dry-run. It resolves the raster dependencies.
  • pytest, mypy and ruff pass locally.
  • After merging, publish with gh release create v0.2.0 --target main --generate-notes.

🤖 Generated with Claude Code

Bump the version to 0.2.0 in pyproject.toml, uv.lock and
memmap/__init__.py, and add a test that fails when __version__ and
pyproject.toml disagree, since `uv version --bump` leaves the former.

Restructure the README around the two ways to get a config, writing it
by hand or generating it with from-elf, with one quick start and a
section for each. Show how to install the raster extra from a release.

Describe the release strategy in RELEASING.md: releases are cut from
main through a short-lived release-prep branch, and the tag goes on the
merged commit on main.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@iharhl
iharhl merged commit d8bb206 into main Nov 8, 2026
3 checks passed
@iharhl
iharhl deleted the release-prep/v0.2.0 branch November 8, 2026 13:04
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