Post release for 1.0.1 + some documentation#3382
Post release for 1.0.1 + some documentation#3382jeromekelleher merged 2 commits intotskit-dev:mainfrom
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 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
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
| 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. |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
Can you review these please @benjeffery?