GitHub Actions is set up to automatically build and draft firmware releases.
Set the repository Actions variable OFFICIAL_MESHCORE_VERSION to the current upstream MeshCore release version.
Example:
OFFICIAL_MESHCORE_VERSION=v1.2.3This value becomes the base FIRMWARE_VERSION used by the release workflows.
Push one or more of the following tag formats to trigger the matching firmware release workflow:
companion-eastmesh-v1.0.1repeater-eastmesh-v1.0.1room-server-eastmesh-v1.0.1Replace v1.0.1 with the EastMesh release version you want to publish.
Each tag triggers a separate workflow:
companion-eastmesh-* builds companion firmwarerepeater-eastmesh-* builds repeater firmwareroom-server-eastmesh-* builds room server firmwareYou can push one, or more tags on the same commit, and they will all build separately.
During the GitHub Actions build:
FIRMWARE_VERSION comes from OFFICIAL_MESHCORE_VERSIONEASTMESH_VERSION comes from the tagThe final firmware/artifact version string becomes:
v1.2.3-eastmesh-v1.0.1-<commit>Example:
room-server-eastmesh-v1.0.1OFFICIAL_MESHCORE_VERSION=v1.2.3v1.2.3-eastmesh-v1.0.1-abcdefOFFICIAL_MESHCORE_VERSION GitHub Actions variable if upstream has changed.Example:
git tag companion-eastmesh-v1.0.1
git tag repeater-eastmesh-v1.0.1
git tag room-server-eastmesh-v1.0.1
git push origin companion-eastmesh-v1.0.1 repeater-eastmesh-v1.0.1 room-server-eastmesh-v1.0.1
The workflows still accept older tag formats for compatibility:
companion-v1.2.3repeater-v1.2.3room-server-v1.2.3room-server-v1.2.3-eastmesh-v1.0.1However, the recommended EastMesh release format is:
companion-eastmesh-v1.0.1repeater-eastmesh-v1.0.1room-server-eastmesh-v1.0.1