trunk shadow changes: com.unity.netcode.gameobjects - #4120
Conversation
|
|
Codecov ReportAll modified and coverable lines are covered by tests ✅ @@ Coverage Diff @@
## develop-2.0.0 #4120 +/- ##
=================================================
- Coverage 73.94% 73.92% -0.03%
=================================================
Files 172 172
Lines 28099 28099
=================================================
- Hits 20779 20772 -7
- Misses 7320 7327 +7
Flags with carried forward coverage won't be shown. Click here to find out more. see 2 files with indirect coverage changes
|
7117fe6 to
30c85f8
Compare
EmandM
left a comment
There was a problem hiding this comment.
I'm approving the C# changes, but I think @michalChrobot you'll want to take a look at the change in manifest_update.py. It looks like an unrelated change but I'm not sure.
|
Yeah, I'm taking a look now (need to resolve the merge conflict + script compilation failure) |
|
|
||
|
|
||
| [UnityTest] | ||
| [UnityCoreClrExplicitDisabled("https://jira.unity3d.com/browse/UUM-149592", "NGO NetworkVariable serialization codegen not generated for some types on CoreCLR (falls back to FallbackSerializer)")] |
There was a problem hiding this comment.
Interesting issue here because UnityCoreClrExplicitDisabled is trunk specific and doesn't exist in our repo. I will investigate how to add this
There was a problem hiding this comment.
It should be fixed now, I will see once the job pass if it works correctly (those tests should run as usual in our current testing)
…tDisabledAttributeShim.cs to make attribute usage possible
This PR contains changes made to the
trunkcopy ofcom.unity.netcode.gameobjects.This usually means that breaking changes has landed in the
trunkEditor, necessitating matching changes to your package code.trunkis therefore currently running CI tests with the modified shadow package instead of your real package. You must integrate these changes into your package (while maintaining compatibility with older versions of Unity supported by your package), release a new version, and land the new version in the editor manifest before the Package RC deadline, as your package otherwise will not be compatible with the released Editor.The bot commit was created on top of the package release commit, and so this PR contains unrelated older commits. You may need to change the PR target branch (by clicking the pencil icon next to the PR title), or cherrypick the commit to a freshly created branch.
Is this automation useful? Let us know on #devs-pets, where you can also ask any question you might have about shadow packages or this automation.
Note: The
shadow-package/com.unity.netcode.gameobjectsbranch may be force-pushed by automation at any time. If you want to make changes before landing this PR, create your own branch (and PR) to avoid automation overwriting your changes:If further changes are made to the shadow package on trunk, this PR will be updated if still open, or else a new PR will be opened.