Repository navigation
66 lines (54 loc) · 1.81 KB
/
Copy pathpython-publish.yml
File metadata and controls
66 lines (54 loc) · 1.81 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
# This workflow will upload a Python Package to PyPI when a release is created
# For more information, see: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-python#publishing-to-package-registries
name: Upload Python Package to PyPI
on:
release:
types: [published] # Trigger when a release is published
permissions:
contents: read # Read permission for the contents
jobs:
release-build:
runs-on: ubuntu-latest
steps:
# Checkout the repository code
- uses: actions/checkout@v2
# Set up Python
- uses: actions/setup-python@v2
with:
python-version: "3.x"
# Build the distribution package
- name: Build release distributions
run: |
python -m pip install --upgrade pip
pip install build
python -m build
# Upload the distribution artifacts for use in the next job
- name: Upload distributions
uses: actions/upload-artifact@v2
with:
name: release-dists
path: dist/
pypi-publish:
runs-on: ubuntu-latest
needs:
- release-build
permissions:
id-token: write # Necessary permission for trusted publishing
environment:
name: pypi
steps:
# Retrieve the release distributions uploaded in the previous step
- name: Retrieve release distributions
uses: actions/download-artifact@v2
with:
name: release-dists
path: dist/
# Publish the distributions to PyPI
- name: Publish release distributions to PyPI
run: |
python -m pip install --upgrade pip
pip install twine
twine upload --repository pypi dist/*
env:
TWINE_USERNAME: ${{ secrets.PYPI_USERNAME }}
TWINE_PASSWORD: ${{ secrets.PYPI_TOKEN }}