Skip to content

chore: bump version 1.1.1 → 1.2.0 - #53

Merged
HugoFara merged 1 commit into
mainfrom
release/1.2.0
Sep 12, 2026
Merged

HugoFara merged 1 commit into
mainfrom
release/1.2.0

Conversation

@HugoFara

Copy link
Copy Markdown
Owner

Release preparation per CONTRIBUTING.md, everything except the tag and the GitHub release.

  • CHANGELOG.md: [Unreleased] → [1.2.0] - 2026-09-12. The 37 entries are unchanged in content but ordered by weight (public surface first) instead of by landing date; verified as a pure permutation of the body lines.
  • bump-my-version bump minor: pyproject.toml, src/pylinkage/__init__.py, CITATION.cff (version and date-released), plus uv lock.
  • docs/ regenerated with sphinx-build -E -a (a fresh environment — the incremental build on top of the stale .doctrees silently skipped unchanged pages). Removes the orphans the old layout left behind: api/pylinkage.collections, api/pylinkage.joints and the tests/ tree, none of which has a source any more. Site builds with 0 warnings; the Deprecations page and all 12 tutorials are in it.

After merging:

git checkout main && git pull
git tag -a v1.2.0 -m "Release v1.2.0"
git push --tags

then publish the GitHub release for v1.2.0, which triggers PyPI. Once 1.2.0 is on PyPI, HugoFara/leggedsnake#9 and pylinkage-editor#2 can go in — both pin >=1.2.0.

Dates the changelog, orders its entries by weight rather than by the
day they landed, and regenerates the published documentation from a
clean environment. The rebuilt site drops the pages that no longer have
a source: the old api/pylinkage.collections and api/pylinkage.joints
references and the tests/ tree.
@HugoFara
HugoFara merged commit f005f17 into main Sep 12, 2026
9 checks passed
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