github.com/pypiserver
1
0
Fork 1
mirror of https://github.com/pypiserver/pypiserver synced 2024-12-20 13:55:49 +01:00
Code Releases Wiki Activity
849335256e
pypiserver/bin
History
Mitja O f3d6dde371
chore: prepare for renaming to main (#611) 
* chore: adjust gha to use `main`

* chore: adjust `ci_helper`

* chore: adjust README

* chore: add small todos
2024-10-06 22:37:07 +02:00
..
.gitignore Download git-new-workdir for STANDALONE. 2015-09-14 18:47:33 +02:00
bumpver.py chore: cleanup release process (#516) 2023-08-27 16:11:54 +02:00
ci_helper.py chore: prepare for renaming to main (#611) 2024-10-06 22:37:07 +02:00
package.sh fix: deprecated setuptools.py when building in package.sh (#568) 2024-04-25 01:07:24 +02:00
README.md chore: cleanup release process (#516) 2023-08-27 16:11:54 +02:00
update_changelog.sh chore: cleanup release process (#516) 2023-08-27 16:11:54 +02:00

README.md

Build scripts folder

Highlight files

  • bumpver.py : Bump, commit and tag new project versions
  • package.sh : Build deployable artifact (wheel) in /dist/ folder.

Fully manual release check-list

  1. Update /CHANGES.rst (+ Title + Date).

  2. Push to GitHub to run all TCs once more.

  3. Bump version: commit & tag it with /bin/bumpver.py. Use --help.

    💡 Read PEP-440 to decide the version.

  4. Push it in GitHub with --follow-tags.

Manually publishing a new package

  1. Generate package wheel with /bin/package.sh.

  2. Upload to PyPi with twine upload -s -i <gpg-user> dist/*

  3. Ensure that the new tag is built on hub.docker.com as latest and as a direct tag reference.

  4. Copy release notes from /CHANGES.rst in GitHub as new "release" page on the new tag.

    💡 Check syntactic differences between .md and .rst files.