wtclaude
8828382e41
A .patch file does not carry enough for an installer to run the tier safely. The installer additionally needs to know which patches form one all-or-nothing unit (the two vendor-sale patches are useless apart), which companion .cs may only be copied once that unit has landed, whether the change needs a core solution rebuild or just ServUO's dynamic script build, and what capability an operator loses by declining. None of that is derivable from the diffs. patches/tier.json declares it, and release.yml folds it into manifest.json as `patch_tier` — so a new or changed patch regenerates release metadata rather than requiring an installer release, which is the same rule §7.1 already applies to the bundle. The staged copy is removed from patches/ so the tarball carries exactly one statement of the table. The release gate now checks the table in both directions: every .patch described by exactly one feature, every named patch and companion present, every declared target equal to the file the diff actually edits, and every rebuild kind one the installer understands. All four were previously invisible until someone ran the tier on a live shard. Refs: docs/installer/PLAN.md §2.2, §7.0 Co-Authored-By: Claude <noreply@anthropic.com>
70 lines
2.6 KiB
JSON
70 lines
2.6 KiB
JSON
{
|
|
"_comment": [
|
|
"The patch tier, described for the Runic Gateway installer.",
|
|
"",
|
|
"A .patch file on its own does not say enough to run the tier safely. The installer",
|
|
"additionally has to know which patches form ONE all-or-nothing unit (the two",
|
|
"vendor-sale patches are useless apart), which companion .cs may only be copied once",
|
|
"that unit has landed, whether the change needs a CORE solution rebuild or just the",
|
|
"dynamic script build, and what capability the operator loses by declining. None of",
|
|
"that is derivable from the diffs, so it is declared here.",
|
|
"",
|
|
"This file is the maintainer-facing source of truth. release.yml folds it into",
|
|
"manifest.json as `patch_tier` and removes it from the staged patches/ directory, so",
|
|
"the tarball carries exactly one copy and it is the one the installer reads",
|
|
"(docs/installer/PLAN.md §7.0). CI also asserts that every .patch here is named by",
|
|
"exactly one feature and every named patch and companion exists — adding a patch",
|
|
"without describing it fails the release rather than shipping a tier that silently",
|
|
"ignores it.",
|
|
"",
|
|
"Older installers ignore `patch_tier` entirely, and an installer newer than the",
|
|
"overlay it is deploying falls back to its own built-in copy of this table."
|
|
],
|
|
|
|
"features": [
|
|
{
|
|
"name": "vendor-sale",
|
|
"summary": "vendor.sale events — player-vendor purchases with buyer, owner, item, price and commission",
|
|
"lost": "no vendor.sale events",
|
|
"rebuild": "core",
|
|
"patches": [
|
|
{
|
|
"name": "playervendor-sale-eventsink",
|
|
"file": "playervendor-sale-eventsink.patch",
|
|
"target": "Server/EventSink.cs"
|
|
},
|
|
{
|
|
"name": "playervendor-sale-gump",
|
|
"file": "playervendor-sale-gump.patch",
|
|
"target": "Scripts/Gumps/PlayerVendorGumps.cs"
|
|
}
|
|
],
|
|
"companions": [
|
|
{
|
|
"file": "BridgeVendorSale.cs",
|
|
"install_to": "Scripts/Custom/Bridge/BridgeVendorSale.cs"
|
|
}
|
|
]
|
|
},
|
|
{
|
|
"name": "moderation-audit",
|
|
"summary": "in-game moderation actions ([ban, [kick, [bcast) forwarded to the website as admin.audit",
|
|
"lost": "no in-game moderation audit forwarding",
|
|
"rebuild": "scripts",
|
|
"patches": [
|
|
{
|
|
"name": "commandlogging-event",
|
|
"file": "commandlogging-event.patch",
|
|
"target": "Scripts/Commands/Logging.cs"
|
|
}
|
|
],
|
|
"companions": [
|
|
{
|
|
"file": "BridgeModerationAudit.cs",
|
|
"install_to": "Scripts/Custom/Bridge/BridgeModerationAudit.cs"
|
|
}
|
|
]
|
|
}
|
|
]
|
|
}
|