Skip to content

chore: release 0.9.1 - #2046

Closed
FBumann wants to merge 1 commit into
mainfrom
release/0.9.1
Closed

FBumann wants to merge 1 commit into
mainfrom
release/0.9.1

Conversation

@FBumann

@FBumann FBumann commented Oct 15, 2026

Copy link
Copy Markdown
Collaborator

Prompt: Lets prepare the next release of specsolve.

Note

The following content was generated by AI.

Releases 0.9.1 on merge: two engine fixes (#2028, #2029), parquet sources read at once (#2014), and the rebuilt benchmarks page. A patch release, because nothing since v0.9.0 breaks a model file or an import.

How the notes were edited, and what was checked

The published benchmarks on main were measured at fbc735a, a dev build. To make the page name a release, the published benchmark should run on main right after this merges and v0.9.1 is tagged.

🤖 Generated with Claude Code

https://claude.ai/code/session_01NTByC5UJJWvcFj3mvmv83v


Generated by Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NTByC5UJJWvcFj3mvmv83v
@read-the-docs-community

Copy link
Copy Markdown

Documentation build overview

📚 specsolve | 🛠️ Build #35158704 | 📁 Comparing 11fdfe0 against latest (15f298d)

  🔍 Preview build  

1 file changed
± about/changelog/index.html

@codspeed

codspeed Bot commented Oct 15, 2026

Copy link
Copy Markdown

Merging this PR will not alter performance

✅ 104 untouched benchmarks
⏩ 307 skipped benchmarks1


Comparing release/0.9.1 (11fdfe0) with main (2588883)2

Open in CodSpeed

Footnotes

  1. 307 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 (15f298d) during the generation of this report, so 2588883 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

@FBumann FBumann closed this Nov 11, 2026
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.

2 participants