Skip to content

save the manifests of an applied deployment, as today's deployment saves them - #24914

Draft
IDCs wants to merge 2 commits into
feat/mod-136from
feat/mod-146
Draft

IDCs wants to merge 2 commits into
feat/mod-136from
feat/mod-146

Conversation

@IDCs

@IDCs IDCs commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor
  • In dev builds, Apply saves the game's deployment manifests from the operations it ran.
  • A path two mod types deploy is listed once, under the type of the mod that deploys it. A mod type left without files has its manifest removed.
  • After a deploy that today's deployment performed, the manifests the new pipeline would generate are compared with the ones the old pipeline saved. The counts are logged and sent as manifest_entry_diff in the planner_plan event.
  • tools/mod-pipeline/fake-skyrimse.mjs starts fresh on every run and --reset only deletes. Its manifests command proves Apply leaves the files and saves the manifests today's deployment does, and a fourth profile holds two mods of different types that deploy one path.

fixes MOD-146
part of MOD-144

@IDCs IDCs self-assigned this Nov 16, 2026
@IDCs
IDCs added this pull request to stack #24915 November 16, 2026 11:41
IDCs added 2 commits November 17, 2026 04:27
…ves them

Apply saves the game's manifests from the operations it ran, as the last step of a run. Manifests generated by the new pipeline are compared against the old pipeline.

fixes MOD-146
--reset only deletes. The manifests command checks the files and manifests Apply leaves against today's deployment's.

part of MOD-144
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