Skip to content

Conversation

@davidmfinol
Copy link
Member

@davidmfinol davidmfinol commented Jun 8, 2025

WSAPlayer builds are failing due to bug in old version. Updating to latest LTS should fix.

Changes

  • Update Unity version, along with Burst version

Successful Workflow Run Link

PRs don't have access to secrets so you will need to provide a link to a successful run of the workflows from your own
repo.

  • ...

Checklist

  • Read the contribution guide and accept the
    code of conduct
  • Docs (If new inputs or outputs have been added or changes to behavior that should be documented. Please make a PR
    in the documentation repo)
  • Readme (updated or not needed)
  • Tests (added, updated or not needed)

Summary by CodeRabbit

  • Chores

    • Updated Unity project version to 2021.3.45f1.
    • Upgraded package dependencies: "com.unity.burst" to 1.8.22, "com.unity.ide.visualstudio" to 2.0.23, and "com.unity.test-framework" to 1.1.33.
  • Tests

    • Updated test cases to match the new Unity version string.

@coderabbitai
Copy link

coderabbitai bot commented Jun 8, 2025

📝 Walkthrough

Walkthrough

The changes update Unity version references and package dependencies across test files and project configuration. Test expectations now reflect Unity version 2021.3.45f1. The Unity manifest and lock files are updated to newer package versions, and the project version file records the new Unity editor version and revision.

Changes

Files/Paths Change Summary
src/model/unity-versioning.test.ts Updated test expectations to Unity version 2021.3.45f1 instead of 2021.3.4f1.
test-project/ProjectSettings/ProjectVersion.txt Changed Unity editor version and revision to 2021.3.45f1.
test-project/Packages/manifest.json Bumped com.unity.burst to 1.8.22 and com.unity.ide.visualstudio to 2.0.23.
test-project/Packages/packages-lock.json Updated versions: com.unity.burst to 1.8.22, com.unity.ide.visualstudio to 2.0.23,
and com.unity.test-framework to 1.1.33; added a dependency for com.unity.burst.

Poem

In the warren, code hops anew,
Unity’s version jumps—forty-five, not four, it’s true!
Packages fresh as springtime dew,
Lock files snug, dependencies too.
The tests all cheer, “We match the crew!”
🐇✨

✨ Finishing Touches
  • 📝 Generate Docstrings

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.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
test-project/ProjectSettings/ProjectVersion.txt (1)

2-2: Optional: Align revision hash in parse test sample

The revision in ProjectVersion.txt (0da89fac8e79) differs from the hash used in the parse test (cb45f9cae8b7). Although it doesn't affect functionality, aligning the sample in unity-versioning.test.ts may reduce confusion.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 65607f9 and 9bcf76e.

⛔ Files ignored due to path filters (3)
  • dist/index.js.map is excluded by !**/dist/**, !**/*.map
  • test-project/ProjectSettings/ProjectSettings.asset is excluded by !**/*.asset
  • yarn.lock is excluded by !**/yarn.lock, !**/*.lock
📒 Files selected for processing (4)
  • src/model/unity-versioning.test.ts (2 hunks)
  • test-project/Packages/manifest.json (1 hunks)
  • test-project/Packages/packages-lock.json (3 hunks)
  • test-project/ProjectSettings/ProjectVersion.txt (1 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (1)
src/model/unity-versioning.test.ts (1)
src/model/unity-versioning.ts (1)
  • UnityVersioning (4-32)
⏰ Context from checks skipped due to timeout of 90000ms (20)
  • GitHub Check: StandaloneLinux64 on 2021.3.32f1
  • GitHub Check: StandaloneWindows64 on 2021.3.32f1
  • GitHub Check: StandaloneWindows64 on 2023.2.2f1
  • GitHub Check: tvOS on 2023.2.2f1
  • GitHub Check: StandaloneWindows64 on 2023.2.2f1
  • GitHub Check: StandaloneWindows64 on 2021.3.32f1
  • GitHub Check: Android on 2023.2.2f1
  • GitHub Check: tvOS on 2021.3.32f1
  • GitHub Check: WSAPlayer on 2021.3.32f1
  • GitHub Check: Android on 2022.3.13f1
  • GitHub Check: WSAPlayer on 2022.3.13f1
  • GitHub Check: StandaloneWindows64 on 2022.3.13f1
  • GitHub Check: tvOS on 2022.3.13f1
  • GitHub Check: WSAPlayer on 2023.2.2f1
  • GitHub Check: Android on 2021.3.32f1
  • GitHub Check: iOS on 2022.3.13f1
  • GitHub Check: iOS on 2021.3.32f1
  • GitHub Check: StandaloneOSX on 2022.3.13f1
  • GitHub Check: StandaloneOSX on 2023.2.2f1
  • GitHub Check: StandaloneOSX on 2021.3.32f1
🔇 Additional comments (8)
test-project/ProjectSettings/ProjectVersion.txt (1)

1-2: Consistency of Unity version bump

The editor version and revision hash have been updated to 2021.3.45f1 (0da89fac8e79), matching the target LTS release. Ensure this version aligns with all related test snapshots and documentation.

test-project/Packages/manifest.json (1)

3-4: Approve package version bumps

The com.unity.burst and com.unity.ide.visualstudio dependency versions have been updated to 1.8.22 and 2.0.23 respectively, aligning with the Unity LTS upgrade. Verify compatibility with existing code and ensure no API-breaking changes.

src/model/unity-versioning.test.ts (3)

10-12: Update parse test for new Unity version

The parse test now reflects 2021.3.45f1, ensuring the regex still captures the version correctly. No further changes are needed as the revision hash is ignored by the regex.


28-28: Update read test for new project version

The read test now expects 2021.3.45f1 when reading from ./test-project, matching the updated ProjectVersion.txt.


34-35: Update determineUnityVersion default test

The default behavior now returns 2021.3.45f1 for 'auto', in sync with the updated project files.

test-project/Packages/packages-lock.json (3)

3-10: Approve com.unity.burst lock update

The lock file now pins com.unity.burst to 1.8.22 and adds com.unity.modules.jsonserialize as a dependency, in accordance with the manifest. Ensure the new modules are present and compatible.


21-21: Approve com.unity.ide.visualstudio lock update

The lock file version for com.unity.ide.visualstudio is updated to 2.0.23 as per the manifest. No additional changes needed.


37-37: Approve com.unity.test-framework lock bump

The com.unity.test-framework package is now at 1.1.33, matching the new dependency graph. This aligns with the burst and editor version upgrades.

@github-actions
Copy link

github-actions bot commented Jun 8, 2025

Cat Gif

@codecov
Copy link

codecov bot commented Jun 8, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 37.05%. Comparing base (65607f9) to head (9bcf76e).
Report is 1 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main     #711   +/-   ##
=======================================
  Coverage   37.05%   37.05%           
=======================================
  Files          77       77           
  Lines        3163     3163           
  Branches      626      626           
=======================================
  Hits         1172     1172           
  Misses       1991     1991           
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@GabLeRoux GabLeRoux merged commit 0b822c2 into main Jun 8, 2025
57 of 60 checks passed
@GabLeRoux GabLeRoux deleted the updateUnityVersion branch June 8, 2025 15:00
@coderabbitai coderabbitai bot mentioned this pull request Jun 9, 2025
4 tasks
@webbertakken
Copy link
Member

Released in v4.6.0

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.

4 participants