Skip to content

fix(mcpp): mark all platforms res_versioned (consistent XLINGS_RES auto-bump) - #337

Merged
Sunrisepeak merged 1 commit into
mainfrom
fix/mcpp-res-versioned
Jul 1, 2026
Merged

fix(mcpp): mark all platforms res_versioned (consistent XLINGS_RES auto-bump)#337
Sunrisepeak merged 1 commit into
mainfrom
fix/mcpp-res-versioned

Conversation

@Sunrisepeak

Copy link
Copy Markdown
Member

Why

Enables the mcpp release pipeline's automated index bump (mcpp-community/mcpp#194) to produce entries consistent with how mcpp is actually maintained.

Today pkgs/m/mcpp.lua is inconsistent:

  • linux: opted into the bot via url_templateversion-check.py --apply would emit ["<ver>"] = { url = github.com/mcpp-community/..., sha256 }github-only, no CN/GitCode fallback, and unlike every existing entry.
  • macosx / windows: no marker → the bot skips them (manual bumps).
  • Yet all existing entries are ["<ver>"] = "XLINGS_RES" (mcpp is mirrored to xlings-res/mcpp).

What

Drop linux's url_template, add res_versioned = true to all three platforms. Now version-check.py --apply --only mcpp appends ["<ver>"] = "XLINGS_RES" on all three and bumps latest.ref — matching the existing convention (and how xlings itself is configured).

Safe

The client never reads platform-level url_template (verified: src/core/xim/installer.cppm only expands version-entry-level Scheme-C templates; mcpp resolves via the XLINGS_RES sentinel → build_xlings_res_url_). Only the bot reads it. Not related to the github-gh V2 url_template migration (#347).

Verified

Simulated --apply --only mcpp against a rolled-back copy → {'linux':'XLINGS_RES','macosx':'XLINGS_RES','windows':'XLINGS_RES'}, latest.ref bumped. lua parse OK.

Companion: openxlings/xlings#349, mcpp-community/mcpp#194.

…to-bump)

mcpp is mirrored to xlings-res/mcpp and all version entries are XLINGS_RES
sentinels, but only the linux block was bot-opted-in — via url_template, which
makes version-check.py emit url+sha256 (github-only, no CN/GitCode fallback),
inconsistent with the existing entries; macosx/windows had no marker at all so
the bot skipped them (manual bumps).

Replace linux's url_template with res_versioned=true and add it to
macosx/windows. Now version-check.py --apply --only mcpp appends
["<ver>"]="XLINGS_RES" on all three platforms and bumps latest.ref,
matching how mcpp is actually maintained (and how xlings itself works).

The client never reads platform-level url_template (only the bot does; client
resolves via the XLINGS_RES sentinel), so dropping it is safe. Enables the
mcpp release pipeline's automated bump (mcpp-community/mcpp#194) to produce
correct, mirror-backed entries.
@Sunrisepeak
Sunrisepeak merged commit a1d660e into main Jul 1, 2026
8 checks passed
@Sunrisepeak
Sunrisepeak deleted the fix/mcpp-res-versioned branch July 1, 2026 14:09
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.

2 participants