菜单
Update Vintage Story CI dependency versions, upload matching game DLLs to vs-build-dependencies, and verify GitHub Actions builds against the current stable game version.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/BASIC-BIT/Vintage-Story-Mods --skill vintage-story-ci-dependencies命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Roleplay community culture and player intent behind The BASICs chat features.
Roleplay community culture and player intent behind The BASICs chat features. Read before designing, defaulting, gating, or writing copy for any RP-facing surface. Captures how RP players actually use these features, which is often not inferable from the code.
Prepare owner-reviewed Vintage Story release changelogs and automate ModDB uploads using Playwright when direct API upload is unavailable.
正在显示 SKILL.md
基于 SOC 职业分类
| name | vintage-story-ci-dependencies |
| description | Update Vintage Story CI dependency versions, upload matching game DLLs to vs-build-dependencies, and verify GitHub Actions builds against the current stable game version. |
| compatibility | opencode |
| metadata | {"audience":"maintainers","domain":"ci-release-ops"} |
Keep CI building against the intended Vintage Story version by aligning three things:
VS_VERSION values in GitHub Actions workflowsUse this workflow when:
vs-build-dependencies.1.x.y.scripts\upload-vs-dependencies.ps1 or workflow VS_VERSION values are changed.git status --short before making changes.BASIC-BIT/vs-build-dependencies as a separate repository with contributor-facing impact.vs-build-dependencies.Vintage-Story-Mods.env values, or secret-bearing clone URLs.Check the official latest stable Windows server version:
$metadata = Invoke-RestMethod -Uri "https://api.vintagestory.at/stable.json"
$latest = $metadata.PSObject.Properties |
Where-Object { $_.Value.windowsserver -and $_.Value.windowsserver.latest -eq 1 } |
Sort-Object { [version]$_.Name } -Descending |
Select-Object -First 1
$latest.Name
Check the local game install version:
& "D:\Games\Vintagestory\Vintagestory.exe" --version
If the local install is behind the official latest stable, stop and ask the maintainer whether to update the local install first or target the installed version temporarily.
List available dependency versions:
gh api repos/BASIC-BIT/vs-build-dependencies/contents --jq '.[].name'
Check a specific version directory:
gh api repos/BASIC-BIT/vs-build-dependencies/contents/1.22.2 --jq '.[].name'
Expected contents for a valid dependency version:
coremodslibREADME.mdversion-info.jsonOnly run this after explicit maintainer approval.
Use the local install as the source of the DLLs:
powershell -NoProfile -ExecutionPolicy Bypass -File "scripts\upload-vs-dependencies.ps1" -VsInstallPath "D:\Games\Vintagestory" -VsVersion "1.22.2"
The upload script will:
BASIC-BIT/vs-build-dependenciescore, mods, and libmain in the dependency repositoryAfter upload, verify the version is visible through the GitHub API before changing CI.
Update all workflow VS_VERSION values together:
.github/workflows/build.yml.github/workflows/codeql.yml.github/workflows/release.ymlUpdate the upload script default so future runs use the same version:
scripts/upload-vs-dependencies.ps1Do not update only one workflow. A partial update leaves release, build, and CodeQL using different game DLLs.
Use the repo-local .NET 10 SDK when available. The system dotnet may be .NET 9 and fail on net10.0.
$env:VINTAGE_STORY = "D:\Games\Vintagestory"
& "D:\bench\vs\.dotnet\dotnet.exe" build "mods-dll\thebasics\thebasics.csproj" --configuration Release /p:GITHUB_ACTIONS=true
If the local .NET 10 SDK path is unavailable, use actions/setup-dotnet behavior as the reference and install or locate a .NET 10 SDK before concluding the build is broken.
Before committing, inspect only the intended files:
git diff -- .github/workflows/build.yml .github/workflows/codeql.yml .github/workflows/release.yml scripts/upload-vs-dependencies.ps1
Commit only those files:
git add -- .github/workflows/build.yml .github/workflows/codeql.yml .github/workflows/release.yml scripts/upload-vs-dependencies.ps1
git commit -m "Update CI to Vintage Story 1.22.2 dependencies"
Push only after explicit maintainer approval:
git push origin main
If branch protection is bypassed, report that explicitly in the summary.
List new runs for the pushed SHA:
gh run list --branch main --limit 5 --json databaseId,workflowName,status,conclusion,headSha,url,createdAt
Watch the relevant runs:
gh run watch <run-id> --exit-status
At minimum, verify:
If a run still fails at dependency download, check:
VS_VERSION matches the uploaded dependency folder name exactlyVS_DEPS_TOKEN can access BASIC-BIT/vs-build-dependenciescore, mods, and lib under that versionIf a run gets past dependency download and fails later, classify it as a separate CI gate. Examples:
Report clearly whether the original dependency problem is fixed before discussing later failures.
Use a concise final summary:
Updated CI to build against Vintage Story <version>.
- Official latest stable: <version>
- Local install: <path> reports <version>
- Uploaded dependencies: BASIC-BIT/vs-build-dependencies@<sha>
- Updated workflows/scripts: <commit sha>
- Local build: <result>
- GitHub Actions: CodeQL <result>, Build <result>
Remaining failures, if any, are <related/unrelated> to dependency setup: <short reason>.