Repository navigation
Say when a build needs one runner per platform, and document the workflow's inputs - #922
Merged
manuelmayer-dev merged 1 commit intoSep 17, 2026
Merged
Conversation
…flow's inputs The CI page opened with a matrix, so splitting the build read like the way to build a plugin in CI. It is not: `build` without `--rid` builds every runtime identifier the manifest declares from one Linux runner, and only a target that cannot be cross-built - a net10.0-windows target, a native library, a build step needing Windows or macOS tooling - needs a runner per platform. The page now says so before the matrix, and points at build-per-platform for anyone publishing through publish-plugin.yml rather than writing the matrix by hand. The release workflow reference had grown stale: it listed eight of the workflow's fifteen inputs. It now lists them all, including build-per-platform and runners, with a section on what splitting the build changes. `--prerelease` also stopped meaning "the newest one": SemVer orders `beta` before `preview`, so it resolves to 3.0.0-preview.10 while the newest release is 3.0.0-beta.11 - which is the one that has `merge`. The CI examples install by version, and the CLI's install page says why. Every other install snippet still says `--prerelease`; they want the prerelease labels fixed, not a pinned version each.
manuelmayer-dev
deleted the
docs/per-platform-build-and-workflow-inputs
branch
September 17, 2026 20:28
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to the
build-per-platformsupport in Macro-Deck-App/GitHub-Actions#3. The docs describedmergeandbuild --ridcorrectly, but never said when a build needs them - and the CI page opened with a matrix, which reads as the way to build a plugin in CI.cli/ci.mdbuildwithout--ridbuilds every declared runtime identifier from one Linux runner; split only for a target that cannot be cross-built (net10.0-windows, a native library, a build step needing Windows or macOS tooling). Rule of thumb: if a plainbuildsucceeds on Ubuntu, you do not need the matrix.build-per-platformfor anyone publishing throughpublish-plugin.yml, instead of hand-writing the matrix.--version 3.0.0-beta.11, and the note explains why--prereleaseis no longer the newest one.creator-portal/release-workflow.mdbuild-per-platform,runners,run-tests,test-path,run-stub-host,platform-url,audiencewere missing, andcli-version's default wasnewest prerelease, which is no longer what the action does.upload-artifactkeeps the merged package, the runner-per-platform table,runners, no fail-fast) and whatmergerefuses.cli/index.mdThe install page claimed only
-previewversions are published. SemVer ordersbetabeforepreview, so--prereleaseresolves to3.0.0-preview.10while the newest release is3.0.0-beta.11- the one that hasmerge. The page now says so and gives the--versioninstall.Not in this PR
introduction/quickstart.md,introduction/manual-setup.md,guides/troubleshooting.md,reference/sdk-packages.mdandsdk/src/MacroDeck.Plugin.Cli/README.mdstill install with--prerelease, so they all hand outpreview.10. Pinning3.0.0-beta.11in each would go stale on the next release; the real fix is a prerelease label that sorts afterpreview(or a stable/rc). Worth doing before 3.0 either way.Verified:
npm run buildindocs/- 120 pages, all internal links valid.