Skip to content

🤖 Auto-update client-publicized redist files#612

Closed
rocketmodfixadmin wants to merge 1 commit into
masterfrom
redist-update/client-publicized
Closed

🤖 Auto-update client-publicized redist files#612
rocketmodfixadmin wants to merge 1 commit into
masterfrom
redist-update/client-publicized

Conversation

@rocketmodfixadmin
Copy link
Copy Markdown
Contributor

Automated Redist Update - client-publicized

This PR contains automatically updated redist files for the client-publicized variant.

Changes

Sync client-publicized redist manifest (no tracked file changes)

Validation

🔄 Validation (file presence, SHA-256 hashes, version monotonicity) runs automatically on this PR.


Triggered by: Scheduled run
Variant: client-publicized
Branch: redist-update/client-publicized

Automatically created by the Unturned Redist update workflow.

sunnamed434 added a commit that referenced this pull request May 31, 2026
…anifest only

Verification of PR #612 showed the changed Assembly-CSharp.dll is a REAL change
(+34 types, +306 methods, +110 KB IL) under an UNCHANGED game version (3.26.3.2),
surfaced because the old manifest tracking stored a wrong value (7693749937906650523
was recorded for client-publicized + server + server-publicized — across two
different Steam apps), which my manifest-extraction fix corrected.

Since NuGet can't republish an existing version, regenerated DLLs under an
unchanged game version are unpublishable (409) and just cause git/nuget drift.
When the tool writes no .commit (no version bump), discard the regenerated files
in the variant dir and keep ONLY the corrected Steam manifest id, so the build is
recorded (stops re-processing) without an unpublishable DLL churn. Real DLL
updates publish on the next game-version bump. Preview variants are unaffected
(their build-id version always bumps).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@github-actions github-actions Bot locked as resolved and limited conversation to collaborators May 31, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants