}
        return acceptedApiChanges
    }

    Map<String, String> toAcceptedChangesMap() {
        acceptedChanges.collectEntries { change ->
            [(new Gson().toJson(change.key)): change.value]
        }
    }

    static Map<ApiChange, String> fromAcceptedChangesMap(Map<String, String> acceptedChanges) {
        acceptedChanges.collectEntries { key, value ->

          <name>configuration</name>
          <description>The place and syntax used to change the value of this expression.</description>
          <type>String</type>
        </field>
        <field>
          <version>1.0.0</version>
          <name>cliOptions</name>
          <description>The command-line switches used to change the value of this expression.</description>
          <type>Properties</type>

things you should know about contributing:

1.  API changes require discussion, use cases, etc. Code comes later.
2.  Pull requests are great for small fixes for bugs, documentation, etc.
3.  Pull requests are not merged directly into the master branch.
4.  Code contributions require signing a Google CLA.

API changes
-----------

We make changes to Guava's public [APIs][], including adding new APIs, very

                "Command should change to SMB_COM_TRANSACTION_SECONDARY");
    }

    @Test
    @DisplayName("Test NT transaction command handling")
    void testNtTransactionCommand() {
        transaction.command = ServerMessageBlock.SMB_COM_NT_TRANSACT;

        // First call
        transaction.nextElement();

        // Second call should change to NT_TRANSACT_SECONDARY

    },
    "tested": {
      "name": "type:tested",
      "colour": "#00ff00",
      "description": "tested"
    },
    "breaking_change": {
      "name": "type:breaking change",
      "colour": "#CF2E1F",
      "description": "breaking change"
    }
  },
  "issue": {
    "with_playground": {
      "requires": 1,
      "conditions": [
        {
          "type": "descriptionMatches",

- [ ] Add request distribution algorithm
- [ ] Create channel synchronization mechanism
- [ ] Implement channel failure detection
- [ ] Add automatic channel recovery
- [ ] Create channel performance monitoring

#### 3.3 Integration Points
- Modify `SmbTransportPool` for multiple connections per session
- Update `SmbSession` for multi-channel awareness
- Enhance `SmbTransport` for channel management

---

## Expected Behavior
<!--- If you're describing a bug, tell us what should happen -->
<!--- If you're suggesting a change/improvement, tell us how it should work -->

## Current Behavior
<!--- If describing a bug, tell us what happens instead of the expected behavior -->
<!--- If suggesting a change/improvement, explain the difference from current behavior -->

## Possible Solution

     * called right before the actual version/artifactScope changes were done. However, a different set of conditionals
     * (and more information) is needed to be able to determine when and if the version and/or artifactScope changes.
     * See the two added methods, manageArtifactVersion and manageArtifactScope.
     */
    @Override

So, having a nice PR title will not only look nice in GitHub, but also in the release notes. 📝

## Add Labels to PRs

            }
        }

        entry.markComplete();
    }

    /**
     * Handle directory change notification
     *
     * @param directoryPath directory path
     * @param childName child file name
     * @param changeType type of change
     */
    public void handleDirectoryChange(String directoryPath, String childName, DirectoryChangeNotifier.DirectoryChangeType changeType) {