Skip to content

release: 0.1.1 — fix a PyPI page that says the package is unpublished - #11

Merged
FZ2000 merged 1 commit into
mainfrom
release/0.1.1
Aug 1, 2026
Merged

release: 0.1.1 — fix a PyPI page that says the package is unpublished#11
FZ2000 merged 1 commit into
mainfrom
release/0.1.1

Conversation

@FZ2000

@FZ2000 FZ2000 commented Aug 1, 2026

Copy link
Copy Markdown
Owner

Problem

https://pypi.org/project/da-sync/ currently tells visitors:

Option B — pip install. Not published yet. Use Option A for now.

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.py0.1.1 (pyproject reads it via attr, so the wheel
    follows automatically)
  • CITATION.cff version + date-released
  • CHANGELOG.md section retitled, with the reason for the release recorded

Verification

Run with a clean Homebrew 3.14 interpreter, asserting it imported the repo's
dacli and not the da-sync copy installed for testing.

check_version_sync earned its place here — it caught three stale spots that
a by-hand bump would have shipped:

After fixing those:

  • check_version_sync --tag v0.1.1 → passes
  • check_version_sync --tag v0.1.0 → refused, "tag 'v0.1.0' does not match
    dacli.version"
    , exit 1. That is the guard release.yml runs before it
    builds anything, so it was worth watching it fire.
  • check_doc_flags, check_doc_references, check_discoverability → pass
  • No test hardcodes a version; test_shim.py and test_cli.py both assert
    against dacli.__version__, so the bump cannot silently break them.

After merge

Tagging v0.1.1 triggers release.yml, which re-checks the tag against the
package version, builds, publishes to PyPI via Trusted Publishing (OIDC) with
PEP 740 attestations, and creates the GitHub release.

🤖 Generated with Claude Code

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]>
@FZ2000
FZ2000 merged commit 0ec879a into main Aug 1, 2026
24 checks passed
@FZ2000
FZ2000 deleted the release/0.1.1 branch August 1, 2026 20:03
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