Skip to content

DIST: Release v0.32.0 - #267

Merged
fumitoh merged 2 commits into
mainfrom
release/v0.32.0
Aug 8, 2026
Merged

DIST: Release v0.32.0#267
fumitoh merged 2 commits into
mainfrom
release/v0.32.0

Conversation

@fumitoh

@fumitoh fumitoh commented Aug 8, 2026

Copy link
Copy Markdown
Owner

Prepares the modelx v0.32.0 release: expanded release notes, updates page entries, and the version bump.

Release notes

doc/source/releases/relnotes_v0_32_0.rst previously covered only the selective ItemSpace invalidation change. It now documents every user-visible change since v0.31.1, in the existing house structure (Enhancements → Backward Incompatible Changes → Bug Fixes → Changes).

Enhancements — serializer version 8, which declares IO specs as literal tuples in a readable _data/iospecs.py instead of pickling them (#266); byte-stable saved models (#265); tolerant model loading, which no longer aborts a read when a pickled value cannot be restored (#255); transactional edits, so a failed add_bases or a new_cells with an unparsable formula leaves the model unchanged; and a clean ValueError for unknown serializer versions.

Backward Incompatible Changes — serializer 8 is now the default write format, so models saved by v0.32.0 cannot be read by earlier releases; version-8 IO spec parameters must be literal-representable; unrelated ItemSpaces are no longer implicitly deleted by an edit; deleting a Space now deletes its live ItemSpaces; add_bases now rejects child-Space/inherited-member name conflicts with NameError; deleting a derived Reference now raises ValueError in all cases.

Bug Fixes — the Cells-rename namespace and collision fixes (#220, #259, #260), derived-Reference deletion, new_space(refs=...) deletion, overriding-Reference recalculation, update_pandas/update_module refmode corruption, the two read_model error-path fixes (#256, #257), pandas 3.0 compatibility, the copy_file retry warning (#82), and the write_model docstring correction.

Changes — Python 3.7 and 3.8 are no longer tested. setup.py metadata is deliberately left at python_requires='>=3.7', matching the precedent from when 3.6 was dropped.

Other changes

  • doc/source/updates.rst: entries for modelx v0.32.0 and for the preceding modelx-cython v0.0.9 release, linking its documentation.
  • modelx/__init__.py: VERSION = (0, 32, 0).
  • devnotes/release_steps.txt removed as outdated.

Verification

  • Full test suite: 1218 passed, 6 skipped.
  • sphinx-build succeeds; the only 3 warnings are pre-existing tutorial pages not in any toctree. Every cross-reference in the new notes resolves to a real page in the built HTML.
  • Every factual claim in the notes was checked against the code, and every "previously" claim against v0.31.1 (and v0.30.1 where serializer compatibility was at stake) by running real saves and reads on worktrees of those tags.

🤖 Generated with Claude Code

fumitoh and others added 2 commits August 8, 2026 18:51
* Expand the v0.32.0 release notes from the ItemSpace-only draft to cover
  every user-visible change since v0.31.1: serializer version 8 (IO specs
  declared as literal tuples, now the default write format), byte-stable
  saved models, tolerant model loading, transactional edits, and the
  Cells-rename, derived-Reference, refmode and read_model error-path fixes.
* Add updates.rst entries for modelx v0.32.0 and for the preceding
  modelx-cython v0.0.9 release, linking its documentation.
* Bump the version to 0.32.0.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The procedure it described no longer matches how modelx is released:
it directs the release commit onto the master branch directly and
predates the current pyproject/CI-based build and upload flow.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@fumitoh
fumitoh merged commit a6c01cb into main Aug 8, 2026
18 checks passed
@fumitoh
fumitoh deleted the release/v0.32.0 branch August 8, 2026 10: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