release: 0.1.1 — fix a PyPI page that says the package is unpublished - #11
Merged
Conversation
The 0.1.0 project page on PyPI still carries the pre-launch README:
**Option B — pip install.** Not published yet. Use Option A for now.
That is on the page of the published package. A project description is
frozen into the uploaded artifact, and PyPI offers no way to edit one, so
the README corrections in #7 and #10 stay invisible to anyone who lands
on PyPI until a new version is uploaded. That is the whole reason for
this release: documentation only, no code changes.
Bumped `dacli.__version__` (pyproject reads it via `attr`), CITATION.cff,
and the CHANGELOG section title.
`check_version_sync` caught three stale spots a manual bump would have
shipped: the generated `docs/reference/cli.md` still embedded 0.1.0, and
two `da-cli 0.1.0` transcripts in getting-started — one of them the
`da --version` block added only yesterday. Regenerated the reference and
corrected both.
Verified with a clean 3.14 interpreter, asserting it imported the repo's
`dacli` rather than the installed one:
* `check_version_sync --tag v0.1.1` passes; `--tag v0.1.0` is refused
with "does not match dacli.__version__", which is the guard
release.yml relies on before it builds anything.
* doc-flags, doc-references and discoverability all pass.
* no test hardcodes a version — they read `dacli.__version__`.
Co-Authored-By: Claude Opus 5 <[email protected]>
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.
Problem
https://pypi.org/project/da-sync/ currently tells visitors:
That is the pre-launch README, on the page of the published package. A
project description is frozen into the uploaded artifact and PyPI provides no
way to edit one, so the README corrections from #7 and #10 remain invisible to
anyone arriving via PyPI until a new version is uploaded.
Solution
A documentation-only release. No code changes beyond the version constant.
dacli/constants.py→0.1.1(pyproject reads it viaattr, so the wheelfollows automatically)
CITATION.cffversion +date-releasedCHANGELOG.mdsection retitled, with the reason for the release recordedVerification
Run with a clean Homebrew 3.14 interpreter, asserting it imported the repo's
dacliand not theda-synccopy installed for testing.check_version_syncearned its place here — it caught three stale spots thata by-hand bump would have shipped:
docs/reference/cli.mdstill embeddedversion 0.1.0(regenerated)docs/getting-started.md:76and:108quotedda-cli 0.1.0, one of themthe
da --versiontranscript added only yesterday in docs: document the PyPI install path in the guides, not just the README #10After fixing those:
check_version_sync --tag v0.1.1→ passescheck_version_sync --tag v0.1.0→ refused, "tag 'v0.1.0' does not matchdacli.version", exit 1. That is the guard
release.ymlruns before itbuilds anything, so it was worth watching it fire.
check_doc_flags,check_doc_references,check_discoverability→ passtest_shim.pyandtest_cli.pyboth assertagainst
dacli.__version__, so the bump cannot silently break them.After merge
Tagging
v0.1.1triggersrelease.yml, which re-checks the tag against thepackage version, builds, publishes to PyPI via Trusted Publishing (OIDC) with
PEP 740 attestations, and creates the GitHub release.
🤖 Generated with Claude Code