Skip to content

Post release for 1.0.1 + some documentation#3382

Merged
jeromekelleher merged 2 commits intotskit-dev:mainfrom
jeromekelleher:post-release
Feb 6, 2026
Merged

Post release for 1.0.1 + some documentation#3382
jeromekelleher merged 2 commits intotskit-dev:mainfrom
jeromekelleher:post-release

Conversation

@jeromekelleher
Copy link
Member

Can you review these please @benjeffery?

@codecov
Copy link

codecov bot commented Feb 6, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.76%. Comparing base (c8fd99f) to head (38f30e6).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3382   +/-   ##
=======================================
  Coverage   89.76%   89.76%           
=======================================
  Files          29       29           
  Lines       31286    31286           
  Branches     5738     5738           
=======================================
  Hits        28083    28083           
  Misses       1794     1794           
  Partials     1409     1409           
Flag Coverage Δ
c-tests 86.77% <ø> (ø)
lwt-tests 80.38% <ø> (ø)
python-c-tests 87.12% <ø> (ø)
python-tests 98.84% <100.00%> (ø)
python-tests-no-jit 33.46% <100.00%> (ø)
python-tests-numpy1 50.24% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
python/tskit/_version.py 100.00% <100.00%> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@jeromekelleher jeromekelleher merged commit dc394d7 into tskit-dev:main Feb 6, 2026
19 checks passed
Comment on lines +1255 to +1261
Once the repo is in a ready state to tag, it is also possible to create the
release directly in the GitHub UI. Click on the "Draft new release" button on
the "releases" page, and update the release notes based on the changelog. Then
set the tag number appropriately (create tag on release) and create the release.
This will trigger the wheel build and should result in the artefacts being
uploaded to PyPI. It is a good idea to go the "actions" tab to check that
this completes and uploads.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pushing a tag generates the release notes automatically, so I'm not sure why we're promoting the manual path? Pushing the tag also releases to test.pypi.org, which is helpful to check before publishing the release.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well I just find the manual approach easier, and I've never checked the tests PyPI ones. We're testing things sufficiently already surely - just writing stuff for future me here really, as I'm likely going to be doing it.

@jeromekelleher jeromekelleher deleted the post-release branch February 6, 2026 15:31
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.

2 participants