Skip to content

chore(main): release 0.0.1-alpha.59 - #447

Merged
fluxopt-release[bot] merged 1 commit into
mainfrom
release-please--branches--main--components--lpspec
Jul 31, 2026
Merged

fluxopt-release[bot] merged 1 commit into
mainfrom
release-please--branches--main--components--lpspec

Conversation

@fluxopt-release

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.0.1-alpha.59 (2026-07-31)

Performance

  • engine: the read-back reads the label order rather than re-imposing it (#446) (53f8eb8)

This PR was generated with Release Please. See documentation.

@fluxopt-release fluxopt-release Bot added the autorelease: pending Release-please owns this one — a release PR awaiting merge label Jul 31, 2026
@fluxopt-release
fluxopt-release Bot enabled auto-merge (squash) July 31, 2026 19:52
@read-the-docs-community

Copy link
Copy Markdown

Documentation build overview

📚 lpspec | 🛠️ Build #33858704 | 📁 Comparing dd9b020 against latest (53f8eb8)

  🔍 Preview build  

1 file changed
± changelog/index.html

@fluxopt-release
fluxopt-release Bot merged commit b13ea1e into main Jul 31, 2026
4 checks passed
@fluxopt-release

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

@fluxopt-release fluxopt-release Bot added autorelease: tagged Release-please owns this one — released, tag pushed and removed autorelease: pending Release-please owns this one — a release PR awaiting merge labels Jul 31, 2026
FBumann added a commit that referenced this pull request Jul 31, 2026
Brings #399 up to `ce0fb3d` — #443, #446, #447, #444 and #448.

**#448 replaced the custom runner with a pytest suite.** `bench/run.py`,
`_run_case.py` and `compare.py` are gone; this branch's `run.py` carried the
duckdb arm and main's `conftest.py` already has it, so the deletion is taken
and nothing is lost. `report.py` keeps main's `.json` reader and this branch's
`--arms`, without which the engine comparison cannot be tabulated at all.

**#446 needed care.** It stopped `_read_back` sorting, because every labelling
path already yields a label-ascending frame and two of them verify it. True of
polars. Not true of a SQL relation: two of duckdb's three label paths are views
over a cross join and SQL promises no order, so inheriting the unsorted
read-back would attach primal values to the wrong coordinates — silently, on a
solve. duckdb's label registry now asks for the order on the way out, where
only a caller reading a solution pays it.

That is the third time today a change free on polars had to be bought here:
`cols` going positional (#433), the read-back (#446), and the registry. The
asymmetry is the branch's most useful finding and is written up in
`bench/duckdb-spike.md`.

781 passed on polars, 780 passed / 5 skipped on duckdb, ruff + pyrefly (0
errors) + mkdocs --strict clean.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

autorelease: tagged Release-please owns this one — released, tag pushed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants