feat(release): auto-publish into xlings ecosystem (res mirror + index bump PR)#349
Merged
Conversation
… bump PR) Close the release→ecosystem gap: on release, besides mirroring binaries and publishing the index artifact, also bump the index SOURCE and open a PR. - tools/mirror_res.sh: generic <project> <version> res mirror (xlings + mcpp), factored out of mirror_xlings_res.sh (now a thin back-compat shim). - tools/bump_index.sh: clone openxlings/xim-pkgindex, delegate the lua edit to the index repo's own version-check.py --apply --only <proj> (contract-agnostic: res_versioned→XLINGS_RES, url_template→url+sha256), open a PR (no auto-merge). - release.yml: new 'bump-index' job (needs create-release), parallel to publish-index/mirror-binaries, using XIM_PKGINDEX_TOKEN. - design doc under .agents/docs/. Rationale + cross-repo plan: .agents/docs/2026-07-01-release-ecosystem-publish-design.md
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
2 participants
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.
What
Closes the release→ecosystem gap. On release, xlings already mirrors binaries to
xlings-res/xlingsand publishes the index artifact — but nothing bumped the index source (pkgs/x/xlings.lua), so the artifact shipped stale (this is exactly how 0.4.61/0.4.62 stalled at 0.4.60; see openxlings/xim-pkgindex#336).This adds the missing step + a reusable, project-generic toolset (shared with mcpp):
tools/mirror_res.sh <project> <version>— generic res mirror (xlings + mcpp asset lists, incl. mcpp.sha256sidecars).mirror_xlings_res.shis now a thin back-compat shim (release.ymlstill calls it by name).tools/bump_index.sh <project> <version>— clonesopenxlings/xim-pkgindex, delegates the lua edit to the index repo's ownversion-check.py --apply --only <proj>(contract-agnostic:res_versioned→XLINGS_RES,url_template→url+sha256; bumpslatest.ref), then opens a PR — no auto-merge. Idempotent (no-op if already current; force-push updates an open PR).release.yml— newbump-indexjob (needs: create-release), parallel topublish-index/mirror-binaries, gated onXIM_PKGINDEX_TOKEN.Design decision
Index git source is intentionally not on the release critical path — availability is guaranteed by the res binary mirror + index artifact. The bump is a PR a maintainer merges; on merge the index repo republishes its artifact and gitee-sync mirrors it.
Verification
version-check.py --apply --only xlings(res_versioned) → appends["<ver>"]="XLINGS_RES"+ bumpslatest.ref(proven by bump(xlings): track 0.4.62 as latest (index stale at 0.4.60) xim-pkgindex#336).bash -nclean on all three scripts;release.ymlparses;bump-indexwired tocreate-release.XIM_PKGINDEX_TOKEN(openxlings/xim-pkgindex, Contents+PR write) in this repo's Actions secrets.Companion
mcpp side (vendored scripts +
publish-ecosystemjob) tracked separately. Full plan:.agents/docs/2026-07-01-release-ecosystem-publish-design.md.