github.com/pypiserver
1
0
Fork 1
mirror of https://github.com/pypiserver/pypiserver synced 2024-11-09 16:45:51 +01:00
Code Releases Wiki Activity
3ba973a85a
pypiserver/bin/README.md
Mitja O 4645f7b10a
chore: cleanup release process (#516) 
* chore: convert bin/README to md

* feat: replace all dates with bumpver

* chore: date in README is now changed by `bumpver`

* chore: clarify the RC workflow

* chore: use global `/tmp` in RC

* chore: slightly prettier description

* chore: move changes file to env

* chore: introduce release_tag workflow

chore(wip): test trigger on PR

chore(wip): add filtered diff

chore(wip): switch to PATTERNS

chore(wip): up to bumpver

chore(wip): temporary disable check

chore(wip): setup python

chore(wip): test with a specific version

chore(wip): test bumpver commit

chore(wip): fix the bumpver usage

chore: cleanup the release_tag workflow

* chore: create draft release from CI

* chore: update the docs

* chore: provide details on the release process

* chore: tiny header update

* chore: remove commented-out code
2023-08-27 16:11:54 +02:00

983 B
Raw Blame History

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.