release: 0.3.1 so compmech-reference-pack reaches PyPI - #10
Merged
Merged
Conversation
compmech-reference-pack is not on PyPI because release.yml fires only on `v*` tags, and the one tag that exists — v0.3.0 — was pushed before the package was merged. `packages/` at that tag holds four directories. The release run succeeded; there were simply four packages to build. v0.3.0 cannot be reused: it produced a public GitHub Release and published four distributions. Moving a tag that people may have pinned or verified is worse than a version bump, so all five packages go to 0.3.1 and the four unchanged ones are republished with no content change. That is the standing cost of the lockstep policy the changelog declares. Two things surfaced while verifying the artefacts: - compmech-reference-pack had no README and no `readme` field, so `twine check` warned on a missing long_description — its PyPI page would have been blank. Added one describing the adapter, the mechdsl extra and the companion statuses. - packages/akms_nodes_gen/README.md still referenced `Packages/AKMS_nodes_gen` four times. The earlier sweep covered docs/ and the root README but not the per-package ones, which become the PyPI landing pages — so those were broken commands on a package's front page, resolving only on a case-insensitive filesystem. Verified: all ten distributions build and pass `twine check` with no warnings; each package's release glob claims exactly its own wheel and sdist; the version audit passes for v0.3.1 and correctly rejects v0.3.0; 1757 tests pass; ruff clean; pyright 0 errors; strict docs build; public-tree audit passes. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TcdE6eeSDBh8xrgKCoGrkw
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
1 participant
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.
compmech-reference-pack is not on PyPI because release.yml fires only on
v*tags, and the one tag that exists (v0.3.0) was pushed before the package was merged.packages/at that tag holds four directories. The release run succeeded; there were simply four packages to build.v0.3.0 cannot be reused: it produced a public GitHub Release and published four distributions. I think that moving a tag that (even if no one had a chance to install it) is a sign of a repo i wouldn't trust, so... version bump!!!
All five packages go to 0.3.1 (4 are republished with no content change.)
That is the standing cost of the lockstep policy the changelog declares. (I should think more before committing my self but....)