W-20408998: sf RNs Dec 3 (#3464)

* Revise release notes for version updates

Updated release notes to reflect version changes and new features.

* Update release notes for Apex test execution fix

Added a fix for running apex tests asynchronously without errors.

Author: jshackell-sfdc

releasenotes/README.md

@@ -25,12 +25,16 @@ Additional documentation:
 * [Salesforce CLI Plugin Developer Guide](https://github.com/salesforcecli/cli/wiki/Quick-Introduction-to-Developing-sf-Plugins)
 * [Salesforce CLI Setup Guide](https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_setup_intro.htm)
 
-## 2.114.5 (Dec 3, 2025) [stable-rc]
+## 2.115.13 (Dec 10, 2025) [stable-rc]
 
 These changes are in the Salesforce CLI release candidate. We plan to include these changes in next week's official release. This list isn't final and is subject to change.
 
 ------------
 
+* FIX: You no longer get an error if you run `apex run test` asynchronously, such as with the `--wait 0` flag, and also specify an output format or `--code-coverage`. (GitHub Issue [#2963](https://github.com/forcedotcom/cli/issues/2963), salesforcedx-apex PR [#596](https://github.com/forcedotcom/salesforcedx-apex/pull/596))
+
+## 2.114.5 (Dec 3, 2025) [stable]
+
 * NEW: (Beta) Specify that you want to run only relevant Apex tests when you deploy metadata to your org with the new `RunRelevantTests` value of the `--test-level` flag of the `project deploy start|validate` and `project delete source` commands.
 
     Salesforce automatically identifies the relevant tests based on an analysis of the deployment payload and the payload dependencies. For fine-grained control, you can also annotate test classes so that they always run in certain conditions. See [@IsTest Annotation](https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_classes_annotation_isTest.htm) in the _Apex Developer Guide_. Each class and trigger in the deployment package must be covered by the executed tests for a minimum of 75% code coverage. This coverage is computed for each class and triggers individually and is different than the overall coverage percentage.
@@ -56,7 +60,7 @@ These changes are in the Salesforce CLI release candidate. We plan to include th
 
 Due to the Thanksgiving break in the United States, we aren't releasing a new stable version. Happy Thanksgiving!
 
-## 2.113.6 (Nov 19, 2025) [stable]
+## 2.113.6 (Nov 19, 2025)
 
 * FIX: We fixed some under-the-hood bugs.