Skip to content

Give 0.1.3 its upload time #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
alkaz-nodemaven merged 1 commit into from
Sep 9, 2026
Merged

Give 0.1.3 its upload time #3

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 21 additions & 8 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,14 +8,27 @@ itself is built on: a change to what the gateway is believed to accept carries
the probe that established it and the date it was run. "The vendor's documentation
says so" is not one of those, and an entry that rests on it says so outright.

## 0.1.3 - not released yet

`__version__` says 0.1.3 as of 2026-09-09 and nothing has been uploaded. The
heading carries no time because the times above are PyPI's upload records and
there is no upload to record; it gets one when a `v0.1.3` tag and a GitHub
Release fire `publish.yml`. Anyone quoting what this library does should say
which tree they read until then, because PyPI still serves 0.1.2 and the two
are different libraries.
## 0.1.3 - 2026-09-09 17:42

Uploaded by `publish.yml` through PyPI Trusted Publishing, from the `v0.1.3`
tag and a published GitHub Release. The publisher on the artifact reads
`nodemaven/nodemaven-python`, workflow `publish.yml`, environment `pypi`; no
token was involved. Wheel 84703 bytes, sdist 155513.

**This is the first release since the repository went public**, so `Source` and
`Issues` reach the PyPI project page for the first time. They have been in
`pyproject.toml` since 0.1.1 and were invisible for two versions, because
project metadata travels with a release and never with a visibility flip.

This heading said `not released yet` for the twenty minutes between the version
bump and the upload, with a paragraph under it explaining that PyPI still served
0.1.2 and that the two trees were different libraries. That was true when
written and false the moment the workflow finished. It is recorded rather than
quietly replaced because it is the same failure this project keeps logging: a
dated claim carried past its date. Twenty minutes is the shortest any of them
has lived, and the lifetime is not the point - the check is, and it is one
request that cannot go stale: `pypi.org/pypi/nodemaven/json` states the version
PyPI is actually serving.

### The library opens sockets now, and the README said it did not

Expand Down
Loading