Repository navigation
chore: Updated aspects of Netcode package in anticipation of v2.13.4 release - #4190
svc-netcode-sdk wants to merge 1 commit into
Conversation
|
Check the configuration's TOML syntax, permitted settings, and size limit. See the error below. Error message: Configuration content:# This is the configuration for the u-pr bot
# https://github.cds.internal.unity3d.com/unity/u-pr
# For configuration of this file:
# https://developer.portal.internal.unity.com/catalog/default/component/u-pr/docs/configuration/automatic_runs/
[github_app]
handle_pr_actions = ['opened', 'ready_for_review'] # PR events that auto-run pr_commands
pr_commands = ["/harness-review"] # what runs on those events
reviewer_commands = ["/harness-review"] # what runs when @u-pr is added as reviewer
|
There was a problem hiding this comment.
💡 Harness Review
The change moves three existing fixes into the 2.13.4 changelog section and advances the package version to 2.13.5. I checked the changelog entries and repository version references and found no actionable issues.
Reviewed commit a5b2f1e
🤖 Helpful? 👍/👎
Codecov ReportAll modified and coverable lines are covered by tests ✅ @@ Coverage Diff @@
## develop-2.0.0 #4190 +/- ##
==============================================
Coverage 74.20% 74.21%
==============================================
Files 172 172
Lines 28200 28200
==============================================
+ Hits 20926 20928 +2
+ Misses 7274 7272 -2
Flags with carried forward coverage won't be shown. Click here to find out more. see 1 file with indirect coverage changes
|
|
Cancelling as we don't have that much to release for now and we are quite focus on Unified Netcode so I will release this once we are done with those big topics (also not a lot to release so it's ok to postpone to later) |
This PR was created in sync with branching of release/2.13.4. It includes changes that should land on the default Netcode branch (develop-2.0.0) to reflect the new state of the package after the v2.13.4 release:
Please review and merge this PR to keep the default branch up to date with the latest package state after the release. Those changes can land immediately OR after the release was finalized but make sure that the Changelog will be merged correctly as sometimes some discrepancies may be introduced due to new entries being introduced meantime