Addressable scene loading

.github/CODEOWNERS

@@ -2,15 +2,10 @@
 # Order is important; the last matching pattern takes the most precedence.
 
 * @Unity-Technologies/multiplayer-sdk
-Profiling/ @Unity-Technologies/multiplayer-tools
-Metrics/ @Unity-Technologies/multiplayer-tools
-/com.unity.netcode.gameobjects/Runtime/Transports/ @Unity-Technologies/multiplayer-workflows
-/com.unity.netcode.gameobjects/Tests/Editor/Transports/ @Unity-Technologies/multiplayer-workflows
-/com.unity.netcode.gameobjects/Tests/Runtime/Transports/ @Unity-Technologies/multiplayer-workflows
-*.asmdef @chrispope @miniwolf @NoelStephensUnity @fluong6
-package.json @chrispope @miniwolf @NoelStephensUnity @fluong6
-AssemblyInfo.cs @chrispope @miniwolf @NoelStephensUnity @fluong6
-.editorconfig @chrispope @miniwolf @NoelStephensUnity @fluong6
-.gitignore @chrispope @miniwolf @NoelStephensUnity @fluong6
-.github/ @chrispope @miniwolf @NoelStephensUnity @fluong6
-.yamato/ @chrispope @miniwolf @NoelStephensUnity @fluong6
+*.asmdef @NoelStephensUnity @EmandM @Unity-Technologies/netcode-qa
+package.json @NoelStephensUnity @EmandM @Unity-Technologies/netcode-qa
+AssemblyInfo.cs @NoelStephensUnity @EmandM @Unity-Technologies/netcode-qa
+.editorconfig @NoelStephensUnity @EmandM @Unity-Technologies/netcode-qa
+.gitignore @NoelStephensUnity @EmandM @Unity-Technologies/netcode-qa
+.github/ @NoelStephensUnity @EmandM @Unity-Technologies/netcode-qa
+.yamato/ @NoelStephensUnity @EmandM @Unity-Technologies/netcode-qa

.github/ISSUE_TEMPLATE/support.md

@@ -7,6 +7,7 @@ assignees: ''
 
 ---
 
-Post your questions or problems here.
+For support related questions we HIGHLY recommend to post a message either on the [Unity Discussions](https://discussions.unity.com/tag/netcode-for-gameobjects) or on our [Discord Community](https://discord.gg/TqNeJTtC) where you can get help from the community and the developers.
+Those forums will get you the fastest response and are the best place to ask for help.
 
-For general questions, networking advice or discussions about the Netcode for GameObjects, you can also reach us on our [Discord Community](https://discord.gg/FM8SE9E) or create a post in the [Unity Multiplayer Forum](https://forum.unity.com/forums/multiplayer.26/).
+If you still feel like you want to open a support issue as an GitHub Issue, please make sure to include as much information as possible (also including any relevant code/project) to help us understand your problem.

.github/pull_request_template.md

@@ -2,8 +2,6 @@
 
 <!-- Add short version of the JIRA ticket to the PR title (e.g. "feat: new shiny feature [MTT-123]") -->
 
-<!-- Add RFC link here if applicable. -->
-
 ## Changelog
 
 - Added: The package whose Changelog should be added to should be in the header. Delete the changelog section entirely if it's not needed.
@@ -26,3 +24,13 @@
 - [ ] Deprecation of the API is explained in the CHANGELOG.
 - [ ] The users can understand why this API was removed and what they should use instead.
 -->
+
+## Backport
+
+<!-- If this is a backport:
+ - Add the following to the PR title: "\[Backport\] ..." .
+ - Link to the original PR.
+If this needs a backport - state this here
+If a backport is not needed please provide the reason why.
+If the "Backports" section is not present it will lead to a CI test failure. 
+-->

.github/renovate.json5

@@ -0,0 +1,37 @@
+{
+  "baseBranches": ["develop", "develop-2.0.0"],
+  "dependencyDashboard": true,
+
+  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
+  "extends": [
+    "local>Unity-Technologies/unity-renovate-config"
+  ],
+  "prConcurrentLimit": 100,
+  // Ignore commits produced by GitHub actions workflows
+  "gitIgnoredAuthors": ["[email protected]"],
+  "ignorePaths": [
+    "**/node_modules/**",
+    // Don't renovate files in special folders using ~ as suffix
+    "**/*~/**",
+    "com.unity.netcode.gameobjects/**/*",
+    "Examples/**/*",
+    "testproject/**/*",
+    "minimalproject/**/*",
+    "testproject-tools-integration/**/*"
+  ],
+  "packageRules": [
+    // Run unity-upm-project and unity-upm-package only on weekends to reduce PR noise
+    // Also ensure dependencies won't be downgraded when they don't exist in the public repositories
+    {
+      "matchManagers": [
+        "unity-upm-project",
+        "unity-upm-package"
+      ],
+      "enabled": "true",
+      "schedule": [
+        "every weekend"
+      ],
+      "rollbackPrs": false,
+    }
+  ],
+}

.github/workflows/assignee-management.yaml

@@ -0,0 +1,70 @@
+# This workflow manages issue assignments and related label changes:
+# 1. When someone is assigned to an issue:
+#    - Removes "stat:awaiting-triage" label
+#    - Adds "stat:Investigating" label
+# 2. When all assignees are removed from an issue:
+#    - Adds "stat:awaiting-triage" label
+#    - Removes "stat:Investigating" label
+# 3. When "stat:Investigating" label is added:
+#    - Automatically assigns the issue to the person who added the label
+
+name: Handle Issue Assignment and Labels
+
+on:
+  issues:
+    types: [assigned, unassigned, labeled]
+
+env:
+  AWAITING-TRIAGE_LABEL: stat:awaiting-triage
+  INVESTIGATING_LABEL: stat:Investigating
+
+jobs:
+  handle_assignment:
+    name: Handle Issue Assignment Changes
+    if: ${{ !github.event.issue.pull_request && github.event.issue.state == 'open' }}
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+
+    steps:
+      - name: Handle Assignment Changes
+        run: |
+          if [[ "${{ github.event.action }}" == "assigned" ]]; then
+            # Someone was assigned - remove awaiting-triage, add investigating
+            echo "ADD=${{ env.INVESTIGATING_LABEL }}" >> $GITHUB_ENV
+            echo "REMOVE=${{ env.AWAITING-TRIAGE_LABEL }}" >> $GITHUB_ENV
+          elif [[ "${{ github.event.action }}" == "unassigned" ]]; then
+            # Check if there are any remaining assignees
+            ASSIGNEES=$(echo '${{ toJson(github.event.issue.assignees) }}' | jq length)
+            if [[ "$ASSIGNEES" == "0" ]]; then
+              # No assignees left - add awaiting-triage, remove investigating
+              echo "ADD=${{ env.AWAITING-TRIAGE_LABEL }}" >> $GITHUB_ENV
+              echo "REMOVE=${{ env.INVESTIGATING_LABEL }}" >> $GITHUB_ENV
+            fi
+          fi
+
+      - name: Update Labels
+        if: env.ADD != '' || env.REMOVE != ''
+        run: gh issue edit "$NUMBER" --add-label "$ADD" --remove-label "$REMOVE"
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GH_REPO: ${{ github.repository }}
+          NUMBER: ${{ github.event.issue.number }}
+
+  handle_investigating_label:
+    name: Handle Investigating Label Addition
+    if: ${{ github.event.action == 'labeled' && github.event.label.name == 'stat:Investigating' && !github.event.issue.pull_request && github.event.issue.state == 'open' }}
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+
+    steps:
+      - name: Assign Issue to person that added Investigating Label
+        run: |
+          # Assign the issue to the person who added the label
+          gh issue edit "$NUMBER" --add-assignee "$ACTOR"
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GH_REPO: ${{ github.repository }}
+          NUMBER: ${{ github.event.issue.number }}
+          ACTOR: ${{ github.actor }}

.github/workflows/backport-verification.yml

@@ -0,0 +1,32 @@
+# This workflow is designed to verify that the pull request description contains a "## Backport" section, which is important as a reminder to account for backports for anyone that works with NGO repository.
+# We have 2 development branches (develop and develop-2.0.0) and we need to ensure that relevant changes are landing in only one or both of them
+# If the "##Backport" section is missing, the workflow will fail and block the PR from merging, prompting the developer to add this section.
+
+# The workflow is configured to run when PR is created as well as when it is edited which also counts simple description edits.
+
+name: "NGO - Backport Verification"
+
+on:
+  pull_request:
+    types: [opened, edited, synchronize, reopened]
+    branches:
+      - develop
+      - develop-2.0.0
+
+jobs:
+  backport-verification:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Check PR description
+        uses: actions/github-script@v7
+        with:
+          script: |
+            const pr = context.payload.pull_request;
+            const body = pr.body || '';
+
+            if (!body.includes('## Backport')) {
+              core.setFailed('PR description must include a "## Backport" section. Please add this section and provide information about this PR backport to develop or develop-2.0.0 branch respectively or explain why backport is not needed.');
+            }

.github/workflows/conventional-pr.yml

@@ -1,6 +1,6 @@
 name: Conventional PR
 
-# Controls when the action will run. 
+# Controls when the action will run.
 on:
   pull_request:
     branches:
@@ -17,7 +17,7 @@ jobs:
     steps:
       - name: semantic-pull-request
         # Internal Unity mirror available at jesseo/action-semantic-pull-request, but actions from private repos aren't supported, so continue to use the public one below
-        uses: amannn/action-semantic-pull-request@b7a9a97cb10fa6e1ae02647e718798175f6b1f1d
+        uses: amannn/action-semantic-pull-request@v5
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
         with:
@@ -34,4 +34,4 @@ jobs:
           # For work-in-progress PRs you can typically use draft pull requests from Github. However, private repositories on the free plan don't have this option and therefore this action allows you to opt-in to using the special '[WIP]' prefix to indicate this state. This will avoid the validation of the PR title and the pull request checks remain pending. Note that a second check will be reported if this is enabled.
           #wip: # optional
           # When using "Squash and merge" on a PR with only one commit, GitHub will suggest using that commit message instead of the PR title for the merge commit, and it's easy to commit this by mistake. Enable this option to also validate the commit message for one commit PRs.
-          validateSingleCommit: true # optional
+          # validateSingleCommit: true # optional

.github/workflows/conversation-labels.yaml

@@ -0,0 +1,51 @@
+# This workflow will update issues with proper "conversation related" labels. This mean that stat:awaiting-repsonse label will be present after Unity account made comments and stat:reply-needed will be present when user made latest comment
+
+name: Update conversation labels of the issue
+
+# Trigger for the workflow
+# This trigger will populate the github.event object
+# Details on properties are here: https://docs.github.com/en/webhooks/webhook-events-and-payloads?actionType=created#issue_comment
+on:
+  issue_comment:
+    types: [created]
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.event.issue.number }}
+  cancel-in-progress: true
+
+# Define labels here
+env:
+  AWAITING_RESPONSE: stat:awaiting-response
+  REPLY_NEEDED: stat:reply-needed
+
+jobs:
+  conversation_labels:
+    name: Calculate and update conversation labels of the issue
+    if: ${{ !github.event.issue.pull_request && github.event.issue.state == 'open' }}
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+
+    steps:
+      - name: Calculate labels
+        run: |
+
+          if [[ "${{ github.event.comment.author_association }}" == "MEMBER" ]]; then
+            # Unity member commented - add awaiting-response, remove reply-needed
+            echo "ADD=${{ env.AWAITING_RESPONSE }}" >> $GITHUB_ENV
+            echo "REMOVE=${{ env.REPLY_NEEDED }}" >> $GITHUB_ENV
+          else
+            # Non-Unity member commented - add reply-needed, remove awaiting-response
+            echo "ADD=${{ env.REPLY_NEEDED }}" >> $GITHUB_ENV
+            echo "REMOVE=${{ env.AWAITING_RESPONSE }}" >> $GITHUB_ENV
+          fi
+
+      - name: Update labels
+        # This runs a command using the github cli: https://cli.github.com/manual/gh_issue_edit
+        # If $ADD is set, it will add the label, otherwise it will remove the label
+        # There is no need to check if $ADD or $REMOVE is set, as the command will ignore it if it is empty
+        run: gh issue edit "$NUMBER" --add-label "$ADD" --remove-label "$REMOVE"
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GH_REPO: ${{ github.repository }}
+          NUMBER: ${{ github.event.issue.number }}

.github/workflows/mark-stale-issue.yaml

@@ -0,0 +1,39 @@
+# This workflow utilises an existing implementation (https://github.com/actions/stale) that performs the following actions:
+#   1) Adds "stale" label to issues that have "stat:awaiting-response" for more than 30 days meaning that since we don't have enough information we may potentially close such issue
+#   2) Closes issues that have been marked as "stale" for more than 30 days
+
+# This affects only Issues but at some point we may also consider rules for PRs
+
+name: Mark or Close Stale Issues
+
+on:
+  workflow_dispatch:
+  schedule:
+    - cron: '0 0 * * *'  # Runs daily at midnight
+
+jobs:
+  stale:
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+
+    steps:
+      - uses: actions/stale@v9
+        with:
+          # Only mark issues (not PRs) as stale
+          any-of-labels: 'stat:awaiting-response'
+          days-before-stale: 30
+          days-before-close: 30
+          stale-issue-label: 'Stale'
+          exempt-issue-labels: 'stat:import,stat:imported'
+          stale-issue-message: >
+            This issue has been automatically marked as stale because it has been awaiting 
+            response for over 30 days without any activity.
+
+            Please update the issue with any new information or it may be closed in 30 days.
+          close-issue-message: >
+            This issue has been automatically closed because it has been stale for 30 days 
+            without any activity. Feel free to reopen if you have new information to add.
+          # Prevent the action from marking/closing PRs
+          days-before-pr-stale: -1
+          days-before-pr-close: -1

.github/workflows/remove-labels-on-issue-close.yaml

@@ -0,0 +1,40 @@
+# This workflow will remove almost all labels from closed issues beside ones that could be relevant for future tracking like: "port:", "type:", "priority:", "regression" and "stat:imported"
+
+name: Remove labels when issue is closed
+
+on:
+  issues:
+    types: [closed] # We want it to run on closed issues
+
+jobs:
+  remove_labels:
+    name: Calculate and remove issue labels
+    if: ${{ !github.event.issue.pull_request  }} # This is needed to distinguish from PRs (which we don't want to affect)
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+
+    steps:
+      - name: Find labels to remove
+        id: data
+        run: |
+          # Convert labels to array and filter out type: labels
+          LABELS_TO_REMOVE=($(echo "$EXISTING_LABELS" | jq -r '.[] | select(startswith("type:") or startswith("port:") or startswith("priority:") or . == "regression" or . == "stat:imported" | not)'))
+
+          # Only proceed if we have labels to remove
+          if [ ${#LABELS_TO_REMOVE[@]} -gt 0 ]; then
+            echo "REMOVE_LABELS=$(IFS=,; echo "${LABELS_TO_REMOVE[*]}")" >> $GITHUB_ENV
+            echo "HAS_LABELS=true" >> $GITHUB_ENV
+          else
+            echo "HAS_LABELS=false" >> $GITHUB_ENV
+          fi
+        env:
+          EXISTING_LABELS: ${{ toJson(github.event.issue.labels.*.name) }}
+
+      - name: Remove labels
+        if: ${{ env.REMOVE_LABELS != '' }}
+        run: gh issue edit "$NUMBER" --remove-label "$REMOVE_LABELS"
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GH_REPO: ${{ github.repository }}
+          NUMBER: ${{ github.event.issue.number }}

.gitignore

@@ -9,4 +9,6 @@ upm-ci~
 utr
 utr.bat
 .download
+Tools/CI/bin
+Tools/CI/obj