You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All PRs/issues attached to the release are merged.
All the badges on the README are passing.
License information is verified as correct. If you are unsure, please comment below.
Locally rendered documentation contains all appropriate pages, including API references (check no modules are
missing), tutorials, and other human-written text is up-to-date with any changes in the code.
Installation instructions in the README, documentation, and the website are updated.
Successfully run any tutorial examples or do functional testing with the latest Python version.
Grammar and writing quality are checked (no typos).
Install pip install build twine, run python -m build and twine check dist/* to ensure that the package can be built and is correctly formatted for PyPI release.
Please tag the maintainer (e.g., @username) in the comment here when you are ready for the PyPI/GitHub release. Include any additional comments necessary, such as version information and details about the pre-release here:
PyPI/GitHub full-release preparation checklist:
Create a new conda environment and install the rc from PyPI (pip install <package-name>==??)
License information on PyPI is correct.
Docs are deployed successfully to https://<github-username-or-orgname>/<package-name>.
Successfully run all tests, tutorial examples or do functional testing.
Please let the maintainer know that all checks are done and the package is ready for full release.
conda-forge release preparation checklist:
Ensure that the full release has appeared on PyPI successfully.
New package dependencies listed in conda.txt and test.txt are added to meta.yaml in the feedstock.
Close any open issues on the feedstock. Reach out to the maintainer if you have questions.
Tag the maintainer for conda-forge release.
Post-release checklist
Run tutorial examples and conduct functional testing using the installation guide in the README. Attach screenshots/results as comments.
Documentation (README, tutorials, API references, and websites) is deployed without broken links or missing figures.
I know I mentioned that we wouldn't re-package this but let's just quickly do it and close all the issues on the 0.3.0 milestone. I think it will be quite quick and it just keeps things up to date for hte future.
I have made another PR fix: fix documentation on fourigui #95 to fix the documentation, maybe we could make another pre-release to verify if we have fixed the documentation there.
OK. I pushed out a new RC release. Please could you make an issue on scikit-package to do some testing on that dispatch workflow and see if we can fix it? It would be nice to be able to deploy docs from dispatch.
I have made that issue on scikit-package. For the documentation on pre-release, seems it is not reflecting the change made by the last PR #96 since it still displays the undefined module. But I confirmed from my local that indeed we have replaced it to a static one and it displays properly... Is that owning to we might need a full release so that these change on documentation could be reflected?
This is the current pre-release documentation page:
Activity
stevenhua0320 commentedon Apr 4, 2026
sbillinge commentedon Apr 4, 2026
I know I mentioned that we wouldn't re-package this but let's just quickly do it and close all the issues on the
0.3.0milestone. I think it will be quite quick and it just keeps things up to date for hte future.stevenhua0320 commentedon Apr 7, 2026
@sbillinge
PyPIpre-release version.PyPIpytestis running successfully on all tests.sbillinge commentedon Apr 7, 2026
OK, I pushed out
rc.1IF the docs build ok let me know and I will do the full release. You don't need to check everything else over again.sbillinge commentedon Apr 7, 2026
This time I just ran the doc build on dispatch. Let's see if that checks it. Then I can push out an rc and then a full
stevenhua0320 commentedon Apr 7, 2026
It seems that the single workflow fails for some reason, maybe we need to redo that?
sbillinge commentedon Apr 7, 2026
OK. I pushed out a new RC release. Please could you make an issue on scikit-package to do some testing on that dispatch workflow and see if we can fix it? It would be nice to be able to deploy docs from dispatch.
stevenhua0320 commentedon Apr 7, 2026
I have made that issue on
scikit-package. For the documentation onpre-release, seems it is not reflecting the change made by the last PR #96 since it still displays the undefinedmodule. But I confirmed from my local that indeed we have replaced it to a static one and it displays properly... Is that owning to we might need a full release so that these change on documentation could be reflected?This is the current
pre-releasedocumentation page:sbillinge commentedon Apr 8, 2026
no, that was my error. I forgot to pull upstream before making the new tag. I pushed out an rc3 now. Sorry about that. Getting tired here.
stevenhua0320 commentedon Apr 8, 2026
sbillinge commentedon Apr 8, 2026
OK, thanks @stevenhua0320 .
0.3.0got sent.