Skip to content

Give 0.1.3 its upload time - #3

Merged
alkaz-nodemaven merged 1 commit into
mainfrom
changelog-0-1-3-release-time
Sep 9, 2026
Merged

Give 0.1.3 its upload time#3
alkaz-nodemaven merged 1 commit into
mainfrom
changelog-0-1-3-release-time

Conversation

@alkaz-nodemaven

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

Copy link
Copy Markdown
Member

What

CHANGELOG.md still headed the 0.1.3 section not released yet, with a
paragraph under it saying PyPI served 0.1.2 and that the two trees were
different libraries. The tag, the GitHub Release and publish.yml made that
false at 2026-09-09 17:42 UTC.

Why it is worded the way it is

The heading now carries the upload time, like every other heading in the file,
plus two things worth recording on this particular release:

  • The publisher on the artifact reads nodemaven/nodemaven-python, workflow
    publish.yml, environment pypi, read from PyPI's integrity endpoint. So
    Trusted Publishing works and no token was involved.
  • It 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.

The old wording is described rather than quietly replaced, per the house rule.
It is the same failure this project keeps logging - a dated claim carried past
its date - and twenty minutes is the shortest any of them has lived. The
lifetime is not the lesson. The check is, and it is one request that cannot go
stale.

Verified

  • PyPI serves 0.1.3; releases are 0.1.0, 0.1.1, 0.1.2, 0.1.3
  • Clean-venv install from PyPI: version 0.1.3, available() sees the provider
    so the package data shipped, the fold builds
    u-country-us-region-district_of_columbia, nodemaven.api and
    nodemaven.check import
  • 343 tests green

Documentation only, no source change.


Summary by cubic

Updates CHANGELOG.md to give 0.1.3 its actual upload time, replacing the "not released yet" heading that the tag, GitHub Release, and publish.yml made false at 2026-09-09 17:42 UTC. Documentation only, no source change.

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

Review in cubic

The heading read "not released yet" with a paragraph under it explaining that
PyPI still served 0.1.2 and that the two trees were different libraries. The
tag, the Release and publish.yml made that false at 17:42 UTC.

Replaced with the upload record the other headings carry, plus the two facts
worth having on it: the publisher on the artifact reads
nodemaven/nodemaven-python, publish.yml, environment pypi, so Trusted
Publishing works and no token was involved; and this is the first release
since the repository went public, so Source and Issues reach the project page
after two versions of sitting in pyproject.toml unseen.

The old wording is described rather than deleted. It is the same failure
logged repeatedly in this project - a dated claim carried past its date - and
twenty minutes is the shortest one has lived here. The lifetime is not the
lesson; the check is, and it is one request that cannot go stale.
@coderabbitai

coderabbitai Bot commented Sep 9, 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: 0b12b80c-1b4a-4481-8028-c19f5c6c2cd8


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 aa4478a into main Sep 9, 2026
9 checks passed
@alkaz-nodemaven
alkaz-nodemaven deleted the changelog-0-1-3-release-time branch September 9, 2026 17:47
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