Skip to content

build: the platforms comment says what is true - all three build #25

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
A13xB0 merged 1 commit into from
Sep 9, 2026
Merged

build: the platforms comment says what is true - all three build #25

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 9 additions & 4 deletions .github/workflows/build.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,10 +27,15 @@ permissions:

env:
UPSTREAM: meshcore-dev/MeshCore
# Which platforms to publish. Only linux-amd64 is live: the Windows and macOS
# cross-builds do not compile yet (MSIM-44), and shipping a release that is
# missing two thirds of its matrix every night is noise rather than signal.
# Widen it with the PLATFORMS repository variable, no commit needed.
# Which platforms to publish. All three cross-build today for the MeshCore
# versions that matter - the v1.17.x native releases carry linux-amd64,
# darwin-arm64 and windows-amd64 - and the PLATFORMS repository variable is
# set to all three, so that is what a release carries. Old MeshCore tags that
# predate the host port still fail the two cross-targets, and that is
# expected: their release keeps whatever built. The fallback stays at
# linux-amd64, the one target needing no cross toolchain, so a fork with the
# variable unset publishes something rather than failing on two it was never
# set up for.
PLATFORMS: ${{ vars.PLATFORMS || 'linux-amd64' }}

jobs:
Expand Down
Loading