Skip to content

setup-mcpp v1: install mcpp through xlings - #1

Merged
Sunrisepeak merged 1 commit into
mainfrom
feat/v1
Nov 16, 2026
Merged

Sunrisepeak merged 1 commit into
mainfrom
feat/v1

Conversation

@Sunrisepeak

Copy link
Copy Markdown
Member

The first release of the action, v1.

  • action.yml: a composite action. setup.sh performs the steps on Linux, macOS and Windows (Git Bash).
  • Inputs: version, xlings-version (both latest by default), mirror (GLOBAL), toolchains (one mcpp toolchain install argument list per line), cache (false).
  • Outputs: version, cache-hit.
  • Installation: xlings through its own installer (checksum verified, GitHub and GitCode sources); mcpp through xlings install -u -g, with the index refreshed, then read from the CN mirror, then fetched with git when an attempt fails.
  • Cache: ~/.xlings and ~/.mcpp; the key names the operating system, the architecture, both releases (latest resolved by git ls-remote), the toolchain list and mcpp.lock.
  • CI: the latest release on Linux x86_64 and aarch64, macOS and Windows, each building and running a new package; a pinned release with a toolchain line on the CN mirror; a cache save followed by an exact-key restore on Linux and Windows.

The tag v1 is created after the merge.

A composite action: one bash script serves Linux, macOS and Windows.
Inputs version, xlings-version, mirror, toolchains and cache; outputs
version and cache-hit. The cache key names the operating system, the
architecture, both releases, the toolchain list and mcpp.lock. CI runs
the latest release on four hosts, a pinned release with a toolchain on
the CN mirror, and a save and exact-key restore of the cache.
@Sunrisepeak
Sunrisepeak merged commit f77a3b6 into main Nov 16, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant