chore: release 0.1.0

[FBumann]

Prompt: Prepare the release PR

Note

The following content was generated by AI.

This releases 0.1.0, the first final release on PyPI after 0.1.0rc1. Merging it tags v0.1.0, opens the GitHub release, and publishes to PyPI once the pypi environment is approved. The notes name the three breaks since rc1.

The version, what the notes claim, and how they were checked

Why 0.1.0 and not 0.2.0. PyPI holds only 0.1.0rc1, which is a pre-release that a user must pin to get. AGENTS.md says a release that breaks a file or an import raises the minor version. A release candidate is where such breaks are expected before the final version, so this final release stays 0.1.0 and lists each break since rc1. If you want 0.2.0 instead, only the heading changes.

The section

• ## Upcoming version becomes ## 0.1.0 (2026-09-25), and a new empty ## Upcoming version sits above it.
• A short opening says the package is on PyPI, and a paragraph defines spec and model, which specsolve now uses as mathspec 0.2.0 does.
• The three breaks since rc1, from feat!: specsolve requires mathspec 0.2.0 and uses its words spec and model, so an archive holds its spec as spec.yaml #1768:
  • the archive member model.yaml is now spec.yaml;
  • specsolve requires mathspec 0.2.0, where model= is now spec= and mathspec.model is now mathspec.spec;
  • messages now say "spec" for the file.
• The four PR lines since rc1 (docs: the site follows the reader's light or dark setting in its own violet colour, with code, diagrams and footnotes readable in both #1767, feat!: specsolve requires mathspec 0.2.0 and uses its words spec and model, so an archive holds its spec as spec.yaml #1768, docs: every link to the language's documentation points at mathspec.readthedocs.io #1764 and fix: the PyPI page links the docs, issues and changelog, and a stale saved answer says the layout moves before 1.0 #1763) stay as they were. The docs: the site follows the reader's light or dark setting in its own violet colour, with code, diagrams and footnotes readable in both #1767 line came in by merging main, which resolved the conflict on the heading.

Checked

• python -m tools.changelog check, after the merge: "releases 0.1.0 on merge".
• python -m tools.changelog notes 0.1.0 prints the section as the release notes.
• pytest tests/test_changelog.py: 39 passed.
• The recovery step in the notes was run against this tree. An archive with model.yaml is refused with a LayoutError. After its member is renamed to spec.yaml, load_archive reads it and returns the same objective.

Not checked: the release workflow itself, which runs only on merge.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Xh8mtkAfVLEGYCTtwy3oqd

[codspeed]

Merging this PR will not alter performance

✅ 24 untouched benchmarks
⏩ 82 skipped benchmarks¹

---

_{Comparing claude/amazing-cannon-jbui9f (c209de3) with main (8c783ca)²}

Footnotes

1. 82 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

2. No successful run was found on main (21e9eab) during the generation of this report, so 8c783ca was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

[read-the-docs-community]

Documentation build overview

📚 specsolve | 🛠️ Build #34762389 | 📁 Comparing c209de3 against latest (d38ce56)

  🔍 Preview build  

3 files changed

± examples/index.html
± about/architecture/index.html
± about/changelog/index.html