2021-11-16 14:00:16 -08:00
---
2021-11-16 20:05:19 -08:00
id: publish
2021-11-16 14:00:16 -08:00
title: Publishing Meshtastic
sidebar_label: Publishing Meshtastic
---
This document is a WIP.
If you’ d like to do ‘ real’ releases with your changes, the procedure is:
## Device
2021-11-16 19:52:00 -08:00
* edit version.properties and check it into the root project
* run bin/promote-release.sh - this should cause github to start a release build (see the CI actions)
* edit the draft release text and click publish
2021-11-16 14:00:16 -08:00
2021-11-26 18:28:32 -08:00
### Update Protobufs
* cd proto
* git checkout master && git pull
* cd ..
* git add proto
* git commit -m "updating proto submodule to latest"
2021-11-16 14:00:16 -08:00
## Android
2021-11-16 19:52:00 -08:00
TBD
## iOS
TBD
2021-11-16 14:00:16 -08:00
## Python
2021-11-29 19:47:27 -08:00
### Pre-requistes
2021-11-16 19:52:00 -08:00
2021-11-29 19:47:27 -08:00
* Python Packages
* * pip3 install pdoc3
* * pip3 install pygatt
* * pip3 install pandoc
* * pip install twine
* https://pandoc.org/installing.html
* nanopb 0.4.4 installed
### Instructions
* update the proto submodule
2021-11-16 19:52:00 -08:00
* bump the version in setup.py
* run bin/upload-release.sh
2021-11-29 19:47:27 -08:00
I usually just edit setup.py to bump the version number, then run "bin/upload-release.sh" (though you should use bin/test-release.sh for the first time - which is just a dry deploy to the pypi test server). This script does the build (including new docs - which will end up in the git checkin) and upload to pypi. Then I do a git commit/push and tag wit the version number.
2021-11-16 14:00:16 -08:00
:::note
2021-11-29 19:47:27 -08:00
You need permissions in the github project to make a build
:::