Repository navigation
feat!: separate optional demos and expand runtime transform tools - #53
manaporkun wants to merge 56 commits into
Conversation
Add a responsive Level Editor sample, Precision handles, group rotation and uniform scaling. Harden handle ownership and lifecycle cleanup, and verify compatibility across Unity input backends. Document validation and the next demo scenarios for continued development. BREAKING CHANGE: samples move from Core into the separately installed optional demos package. Existing imported sample copies require explicit migration.
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 39825156 | Triggered | Generic High Entropy Secret | 395a256 | ci/test_consumer_project.py | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
|
CI investigation for the two failed consumer jobs on 9613aad (run 43728009379): both failures are a Unity account/license activation lockout, not a code failure. No code fix is needed; the failed jobs will be re-run ( Identical decisive lines in both job logs (2021-legacy tarball job 132856778875 at stage Why this is infra, not 9613aad:
Next: wait for run 43728009379 to finish (5 consumer jobs still running/queued), then |
Core stays independently installable, while the original showcase and four additional samples live in the optional Demos package. Existing sample GUIDs are preserved; users need to back up and remove old imports before importing the relocated showcase or Lamp Assembly.
The branch adds Precision visuals, lifecycle and ownership fixes, opt-in group transform controls and bounded rotation. The optional samples share a UI Toolkit shell and include Level Editor, Modular Building, Lamp Assembly and a gallery. The release workflow freezes Core 4.0.0 and Demos 1.0.0 before testing and publishes only those tested files. An advanced main stops publication, and interrupted releases are revalidated from their original package source.
Consumer CI now installs the frozen packages through real UPM tarball and local Git routes, then checks use, customization, native players, upgrade and removal. The approved coverage is five full journeys and three installation/build/player probes across Unity 2021.3.45f1 and Unity 6, both input backends and Built-in/URP. Frozen fixtures, package hashes, real window input, rendered frames and exact test inventories prevent stale or partial evidence from passing.
November 2026 update: the original plan to run the 2021 journeys on Unity 2021.3.0f1 is not achievable in headless CI with a Personal account. Every activation route was measured failing with redacted licensing output retained in job artifacts: the Editor's bundled 1.9 licensing client misreports a machine-mismatched ULF as activated (so the binding fallback never fires), a current client assigns a seat whose entitlement this Editor's licensing module then rejects, and the Editor's own account activation dies at Unity's deprecated legacy endpoint. With owner approval, the 2021 consumer profile now runs Unity 2021.3.45f1 — the final 2021.3 patch, also the compatibility-floor Editor — through the same GameCI action wrappers as Unity 6, and the minimum-activation prerequisite, licensing-client helper and receipt machinery are deleted. Declared 2021.3.0f1 support is unchanged; it rests on the recorded local macOS candidate validation at that exact version, the 2021.3.45f1 floor/consumer suites, and the narrow min-API lint. CI consumer journeys are not 2021.3.0f1 evidence and are not described as such.
On 25dfe41, all 141 local Python tests, static checks and package-boundary verification pass. Run 42596677952 (attempt 3) is fully green: Remote Core/Demos jobs for both input backends, the Unity 2021.3.45 compatibility floor, minimum API lint, commit hygiene, package validation and all eight Linux consumer journeys pass; the only skips are check-reporting jobs and the main-only publish job. The matrix's first runs found and fixed several latent fixture/driver defects stage by stage (coverage-flag CLI rejection, xdotool sync hang, disabled-handle capture, World/Local key sequence, distinct consumer prefab size, Unity 6 symbol ambiguity, handle-less showcase verification, upgrade prefab-size expectation). Two full journeys initially stopped on Unity's per-account activation rate limit (143.002) after the day's repeated runs and passed unchanged when rerun individually. Earlier Mac and WebGL smoke evidence is documented in the development handoff, and the owner confirmed physical Mac trackpad validation.
Keep this draft until final owner review is complete. Main automatically publishes Core and updates the public WebGL showcase on merge. Asset Store packaging and presentation remain separate work.
BREAKING CHANGE: Core no longer distributes the original sample. Install the optional Demos package explicitly and follow the import cleanup instructions to avoid duplicate GUIDs and assemblies.