-
Notifications
You must be signed in to change notification settings - Fork 577
Fix version label + use secure unity version #321
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix version label + use secure unity version #321
Conversation
Older Unity version had the security vulnerability, so we update it
… workflow" This reverts commit a6ab3d9.
…using built-in license handling
…built-in activation flow
…nse in the long-running container Now we got the license secret to be read, we got this error: "Machine bindings don't match". So it seems that the license I generated locally can't be used. So we need to activate the license within the container
…the license in the long-running container" This reverts commit f6a9aa6.
…image's built-in activation flow" This reverts commit a9f4c02.
…ion and using built-in license handling" This reverts commit 4e5ffc0.
…i/unity-activator" This reverts commit e9520ee.
…I workflow" This reverts commit 01b8879.
WalkthroughUnity version bumped from 2021.3.45f1 to 2021.3.45f2 across CI/CD workflows and project settings. Added a version label UI element to the editor window to display the package version dynamically. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
Poem
Pre-merge checks and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✨ Finishing touches
🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (5)
🧰 Additional context used🧬 Code graph analysis (1)MCPForUnity/Editor/Windows/MCPForUnityEditorWindowNew.cs (1)
🔇 Additional comments (7)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
* chore: update Unity version from 2021.3.45f1 to 2021.3.45f2 Older Unity version had the security vulnerability, so we update it * feat: add dynamic version display in editor window settings * refactor: remove manual license file handling from Unity test workflow * Revert "refactor: remove manual license file handling from Unity test workflow" This reverts commit a6ab3d9. * feat: add Unity license credentials to Docker containers in CI workflow * refactor: replace manual Unity license activation with game-ci/unity-activator * refactor: simplify Unity CI setup by removing game-ci activation and using built-in license handling * fix: improve Unity license activation in CI by using unityci image's built-in activation flow * refactor: activate once in a temporary container, then reuse the license in the long-running container Now we got the license secret to be read, we got this error: "Machine bindings don't match". So it seems that the license I generated locally can't be used. So we need to activate the license within the container * Revert "refactor: activate once in a temporary container, then reuse the license in the long-running container" This reverts commit f6a9aa6. * Revert "fix: improve Unity license activation in CI by using unityci image's built-in activation flow" This reverts commit a9f4c02. * Revert "refactor: simplify Unity CI setup by removing game-ci activation and using built-in license handling" This reverts commit 4e5ffc0. * Revert "refactor: replace manual Unity license activation with game-ci/unity-activator" This reverts commit e9520ee. * Revert "feat: add Unity license credentials to Docker containers in CI workflow" This reverts commit 01b8879.
We also fix the version label in the new UI
Summary by CodeRabbit
Chores
UI Improvements