File tree 1 file changed +13
-17
lines changed
1 file changed +13
-17
lines changed Original file line number Diff line number Diff line change 5
5
pip install -U build
6
6
python3 -m build
7
7
8
- ### Incrementing the lib version
8
+ ## Incrementing the lib version
9
9
10
10
- Edit ` fhirclient/client.py ` and change the ` __version__ ` field.
11
11
- Edit ` docs/Doxyfile ` and change the ` PROJECT_NUMBER ` field.
12
12
13
- ## Docs Generation
13
+ ## Cutting a new release
14
+
15
+ 1 . Make sure that the version is correct in the source (see above for update instructions).
16
+ 2 . Update the docs
17
+ 3 . Release on GitHub
18
+ 4 . Announce on Zulip
19
+
20
+ ### Docs Generation
14
21
15
22
Docs are generated with [ Doxygen] ( https://www.doxygen.nl/ )
16
23
and [ doxypypy] ( https://github.com/Feneric/doxypypy ) .
@@ -24,23 +31,12 @@ I usually perform a second checkout of the _gh-pages_ branch and copy the HTML f
24
31
doxygen docs/Doxyfile
25
32
rsync -a docs/html/ ../client-py-web/
26
33
27
- ## PyPi Publishing (notes for SMART team)
28
-
29
- Using flit (* Note* : Alternatively, you can use [ twine] ( https://twine.readthedocs.io/ ) ):
30
-
31
- ### Make sure that you have the PyPi account credentials in your account
32
-
33
- copy server.smarthealthit.org:/home/fhir/.pypirc to ~/.pypirc
34
-
35
- ### Test the build
36
-
37
- python3 -m build
34
+ ### Release on GitHub
38
35
39
- ### Upload the packages to PyPi
36
+ Just create a new release in GitHub and create a corresponding tag.
40
37
41
- pip install -U flit
42
- flit publish
38
+ This will also cause the ` pypi.yaml ` GitHub Action to fire, uploading to PyPI.
43
39
44
40
### Announce the release
45
41
46
- Make a post in the [ Zulip channel] ( https://chat.fhir.org/#narrow/stream/179218-python ) for python.
42
+ Make a post in the [ Zulip channel] ( https://chat.fhir.org/#narrow/stream/179218-python ) for python.
You can’t perform that action at this time.
0 commit comments