Repository navigation
chore: release 0.14.1 - #180
Merged
Merged
Conversation
- Move the [Unreleased] entries under [0.14.1] and add the compare link. - Reclassify the ModelSchema guard from Added to Fixed: it stops erdify producing a wrong entity rather than adding a capability, which is also what makes this a patch rather than a minor. - Bump the version in pyproject.toml and re-lock. - Point the documented pre-commit `rev` at v0.14.1.
|
🎯 Code Coverage (details) 🔗 Commit SHA: 1d75af7 | Docs | View more details | Give us feedback! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Patch release.
[Unreleased]→[0.14.1]with the compare link, version bump,uv lock, and the documented pre-commitrev:moved tov0.14.1.What ships
Fixed — ninja
ModelSchemano longer drawn as an empty entity (#179). Behaviour introduced hours ago in 0.14.0: anyone passing--base-classes ModelSchemagot an empty box beside the real table. Now detected, skipped, and explained on stderr.Fixed —
frameworks.svgis valid XML again, and the image footer no longer makes the headline's "five" look like a miscount (#178).Changed — the README and docs home open with the five-frameworks image (#176–#178).
One reclassification worth noting
The
ModelSchemaentry moved from### Addedto### Fixed. It stops erdify producing a wrong entity rather than adding a capability — and getting that right is what makes this a patch rather than a minor. A reader scanning the changelog for "do I need this?" gets a truthful answer either way, but the version number only lines up underFixed.Why release now rather than sit on it
Two reasons, and the second is the stronger one:
--base-classesshipped in 0.14.0, so the empty-entity bug is live for anyone who reaches forModelSchema.Nothing in here is risky: one narrow parser guard with 7 tests, and documentation.
Type of change
Verification
uv.lockre-synced in the same commit.After merge
Same flow as before: I tag
v0.14.1, publish the GitHub release and post the announcement Discussion. The PyPI publish then waits in the gatedpypienvironment for your Review deployments → Approve.Checklist
uv run pytestpasses locallyuv run ruff check src/ tests/anduv run mypy src/passCHANGELOG.mdupdated under[Unreleased]