Skip to content

Release 0.1.4 - #5

Merged
alkaz-nodemaven merged 1 commit into
mainfrom
release-0.1.4
Sep 10, 2026
Merged

Release 0.1.4#5
alkaz-nodemaven merged 1 commit into
mainfrom
release-0.1.4

Conversation

@alkaz-nodemaven

@alkaz-nodemaven alkaz-nodemaven commented Sep 10, 2026

Copy link
Copy Markdown
Member

Bumps __version__ to 0.1.4 and dates the CHANGELOG entry. No other change - the content shipped in #4.

Why a release at all. The bug was reported against the README on the PyPI project page, and both halves of the fix travel with a release and never with a push. Measured today, before cutting this:

PyPI serves: 0.1.3
provides_extras: None
requires_dist: ['tomli>=1.1.0; python_version < "3.11"']

So on PyPI right now pip install nodemaven[requests] is a warning and an install without requests, and the quickstart still fails. Same rule 0.1.3 proved in the other direction: Source and Issues sat in pyproject.toml from 0.1.1 and reached the project page only when 0.1.3 shipped, a day after the repository went public.

On the number. 0.1.3.2 was considered and is valid - PEP 440 allows a four-component release segment, packaging.Version accepts it, and it sorts 0.1.3 < 0.1.3.post1 < 0.1.3.1 < 0.1.3.2 < 0.1.4. Rejected because the third component already is the "small fix, nothing broken" signal and no convention reads a fourth as "smaller than a patch" - an unfamiliar number spends a reader's attention on the versioning scheme instead of passing unnoticed, which is what a patch should do. 0.1.3.post1 was rejected on the spec rather than on taste: PEP 440 reserves post-releases for corrections that do not affect the distributed software, and this one adds an installable extra.

Test plan

  • pytest -q - 355 passed, 3 skipped
  • import nodemaven; nodemaven.__version__ -> 0.1.4
  • ci-ok
  • After merge: tag v0.1.4, GitHub Release, publish.yml through Trusted Publishing

Summary by cubic

Releases 0.1.4 so the requests extra fix reaches PyPI users. The fix was already merged but only ships with a release, and PyPI currently serves 0.1.3 without the extra. This bumps __version__ and dates the changelog entry.

Chose 0.1.4 over 0.1.3.post1 because PEP 440 reserves post-releases for corrections that don't affect distributed software, and this adds an installable extra.

Written for commit f2b02fd. Summary will update on new commits.

Review in cubic

The bug was reported against the README on the PyPI project page, and both
halves of the fix travel with a release and never with a push. Measured today
before cutting this, pypi.org/pypi/nodemaven/json reported provides_extras:
None while the merged tree had already declared the extra - so on PyPI
`pip install nodemaven[requests]` is still a warning and an install without it.

Same rule 0.1.3 proved the other way round: Source and Issues sat in
pyproject.toml from 0.1.1 and reached the project page only when 0.1.3 shipped,
a day after the repository went public.

0.1.3.2 was considered. It is valid - PEP 440 allows a four-component release
segment and it sorts between 0.1.3 and 0.1.4 - and was rejected because the
third component already is the "small fix" signal and nothing reads a fourth as
"smaller than a patch". 0.1.3.post1 was rejected on the spec: post-releases are
for corrections that do not affect the distributed software, and this one adds
an installable extra.
@coderabbitai

coderabbitai Bot commented Sep 10, 2026

Copy link
Copy Markdown

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 3fe6c828-8da5-4b99-9a94-854c55004e2d


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@alkaz-nodemaven
alkaz-nodemaven merged commit 9fa05e4 into main Sep 10, 2026
9 checks passed
@alkaz-nodemaven
alkaz-nodemaven deleted the release-0.1.4 branch September 10, 2026 09:33
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