chore: bump the plugin pin to v2.19.2 in all four samples - #16
Merged
Merged
Conversation
All four samples now pin com.displayxr.unity at #upm/v2.19.2, which UPM resolves to 204c4457855ee81f2ac2329ef633dbc35489246d. Previous pin was #upm/v2.19.1 (77eaebf63b334fe6ddc94eb03ed30d9094441a8f). What the bump carries: - #322 - the engine_render_gated sidecar flag, emitted into Builds/Win64/<variant>/<variant>.displayxr.json by the build post-process. All four rebuilt players now carry "engine_render_gated": true. - #323 - overlay-aspect fixes. All four players were rebuilt from scratch with Unity 6000.4.0f1 in batchmode: zero error CS, Build Finished Result: Success, Exiting batchmode successfully now. The shipped displayxr_unity.dll is identical across all four builds (SHA256 6f27704cf6378bb7afbfd7a21699c8ca74f2a2621487e399066e7c7d1d95840c) and Authenticode-Valid, signed CN="Leia, Inc.". packages-lock.json is whatever Unity wrote during those builds, not a hand edit. Editor-generated churn in the OpenXR settings, ProjectSettings and HDRP global settings assets was line-ending-only or unrelated to the pin, and was discarded. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012co2j1fdmZ2AdEAp4Y3xpp
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
1 participant
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.
Bumps com.displayxr.unity from #upm/v2.19.1 to the just-released #upm/v2.19.2
in all four samples, and rebuilds all four Win64 players against it.
What v2.19.2 carries
post-process now writes "engine_render_gated": true into
Builds/Win64/<variant>/<variant>.displayxr.json. Verified present in all
four rebuilt players.
Builds
All four rebuilt from scratch with Unity 6000.4.0f1 in batchmode. Every log
ends with "Build Finished, Result: Success." and "Exiting batchmode
successfully now!", with zero "error CS" lines.
Verification
SHA256 6f27704cf6378bb7afbfd7a21699c8ca74f2a2621487e399066e7c7d1d95840c,
Authenticode status Valid, signer CN="Leia, Inc.", O="Leia, Inc.".
#upm/v2.19.2, hash 204c4457855ee81f2ac2329ef633dbc35489246d.
No player was launched - this is a build-and-verify pass only.
Diff hygiene
packages-lock.json is whatever Unity wrote during the builds, not a hand
edit. The editor also touched the OpenXR settings, ProjectSettings/
GraphicsSettings and the HDRP global settings assets; those diffs were
line-ending-only or unrelated to the pin (an HDRP m_RuntimeSettings rid list
the editor repopulates), so they were discarded. Only the four manifest.json
and four packages-lock.json files are committed.
🤖 Generated with Claude Code
https://claude.ai/code/session_012co2j1fdmZ2AdEAp4Y3xpp