Publish 8.7-20240223135434+0000 (#28210)

gradle/wrapper/gradle-wrapper.properties

@@ -1,6 +1,6 @@
 distributionBase=GRADLE_USER_HOME
 distributionPath=wrapper/dists
-distributionUrl=https\://services.gradle.org/distributions-snapshots/gradle-8.7-20240213015211+0000-bin.zip
+distributionUrl=https\://services.gradle.org/distributions/gradle-8.7-rc-1-bin.zip
 networkTimeout=10000
 validateDistributionUrl=true
 zipStoreBase=GRADLE_USER_HOME

platforms/documentation/docs/src/docs/css/manual.css

@@ -1506,28 +1506,26 @@ path {
 }
 
 .dark-mode {
+    /* Works on Firefox */
+    * {
+      scrollbar-width: auto;
+      scrollbar-color: #686868 #242526;
+    }
 
-	/* Works on Firefox */
-	.docs-navigation {
-		scrollbar-width: auto;
-		overflow-y: scroll;
-		scrollbar-color: #686868 #242526;
-	}
-
-	/* Works on Chrome, Edge, and Safari */
-	.docs-navigation::-webkit-scrollbar {
-		width: 12px;
-	}
+    /* Works on Chrome, Edge, and Safari */
+    *::-webkit-scrollbar {
+      width: auto;
+    }
 
-	.docs-navigation::-webkit-scrollbar-track {
-		background: #242526;
-	}
+    *::-webkit-scrollbar-track {
+      background: #242526;
+    }
 
-	.docs-navigation::-webkit-scrollbar-thumb {
-		background-color: #686868;
-		border-radius: 20px;
-		border: 3px #686868;
-	}
+    *::-webkit-scrollbar-thumb {
+      background-color: #686868;
+      border-radius: 20px;
+      border: 3px #686868;
+    }
 }
 
 /* Custom Admonition Blocks - Icons from https://github.com/primer/octicons */

platforms/documentation/docs/src/docs/userguide/dep-man/06-publishing/publishing_ivy.adoc

@@ -13,7 +13,7 @@
 // limitations under the License.
 
 [[publishing_ivy]]
-= Ivy Publish Plugin
+= The Ivy Publish Plugin
 
 The Ivy Publish Plugin provides the ability to publish build artifacts in the http://ant.apache.org/ivy/[Apache Ivy] format, usually to a repository for consumption by other builds or projects. What is published is one or more artifacts created by the build, and an Ivy _module descriptor_ (normally `ivy.xml`) that describes the artifacts and the dependencies of the artifacts, if any.
 

platforms/documentation/docs/src/docs/userguide/dep-man/06-publishing/publishing_maven.adoc

@@ -13,7 +13,7 @@
 // limitations under the License.
 
 [[publishing_maven]]
-= Maven Publish Plugin
+= The Maven Publish Plugin
 
 The Maven Publish Plugin provides the ability to publish build artifacts to an https://maven.apache.org/[Apache Maven] repository.
 A module published to a Maven repository can be consumed by Maven, Gradle (see <<declaring_dependencies.adoc#declaring-dependencies,Declaring Dependencies>>) and other tools that understand the Maven repository format.

platforms/documentation/docs/src/docs/userguide/optimizing-performance/performance.adoc

@@ -97,9 +97,6 @@ A build whose execution time is dominated by a single subproject won't benefit m
 Neither will a project with lots of inter-subproject dependencies.
 But most multi-subproject builds see a reduction in build times.
 
-For more information about parallel builds, check out the
-<<performance.adoc#parallel_execution,parallel builds documentation>>.
-
 === Visualize parallelism with build scans
 
 Build scans give you a visual timeline of task execution. In the following

platforms/documentation/docs/src/docs/userguide/running-builds/introduction/build_file_basics.adoc

@@ -105,7 +105,7 @@ application {
 
 In this example, the main class (i.e., the point where the program's execution begins) is `com.example.Main`.
 
-Consult the <<writing_build_scripts.adoc#writing_build_scripts,Writing Settings File>> page to learn more.
+Consult the <<writing_build_scripts.adoc#writing_build_scripts,Writing Build Scripts>> page to learn more.
 
 [.text-right]
 **Next Step:** <<dependency_management_basics.adoc#dependency_management_basics,Learn about Dependency Management>> >>

released-versions.json

@@ -1,7 +1,7 @@
 {
   "latestReleaseSnapshot": {
-    "version": "8.7-20240221013628+0000",
-    "buildTime": "20240221013628+0000"
+    "version": "8.7-20240223135434+0000",
+    "buildTime": "20240223135434+0000"
   },
   "latestRc": {
     "version": "8.7-rc-1",

subprojects/performance/README.md

@@ -5,15 +5,15 @@ This project contains the Gradle performance test suite. For information about t
 
 A performance test scenario is made up of 2 parts:
 
-1. A test build to use. The test builds are generated from templates and are defined in the [`build-logic/performance/src/main/groovy/performance-templates.gradle`](build-logic/performance/src/main/groovy/performance-templates.gradle) plugin. 
-2. Details for how to invoke Gradle (or Maven). This includes the tasks to run, the JVM args, whether the daemon or tooling API should be used to invoke Gradle, and so on.
+1. A test build to use. The test builds are generated from templates and are defined in the [`build-logic/performance/src/main/groovy/performance-templates.gradle`](build-logic/performance/src/main/groovy/performance-templates.gradle) plugin.
+2. Details for how to invoke Gradle (or Maven). This includes the tasks to run, the JVM args, whether the daemon or tooling API should be used to invoke Gradle, etc.
 
-A performance test configure various fixtures to describe each scenario. The fixtures will then run the scenario several times to warm up, and then several more times, capturing metrics.
+A performance test configures various fixtures to describe each scenario. The fixtures will then run the scenario several times to warm up and then several more times, capturing metrics.
 The metrics are collected in a database under `~/.gradle-performance-test-data` and a report is generated into `build/performance-tests/report`.
 
 ### Performance test builds
 
-The build templates live in [`src/templates`](src/templates). Each template build is parameterized to some degree. For example, it is possible for define how many projects, source 
+The build templates live in [`src/templates`](src/templates). Each template build is parameterized to some degree. For example, it is possible to define how many projects, source
 or test files to generate for a performance test build.
 
 There is a task defined in [`build-logic/performance/src/main/groovy/performance-templates.gradle`](build-logic/performance/src/main/groovy/performance-templates.gradle) for each performance test build, that specifies which templates to use and the build parameters.
@@ -28,7 +28,7 @@ There is a task defined in [`build-logic/performance/src/main/groovy/performance
 
 ### Report
 
-There is a `performance:report` task that generates a static HTML report from the contents of the database in `~/.gradle-performance-test-data`. This report allows the results over
+A `performance:report` task generates a static HTML report from the contents of the database in `~/.gradle-performance-test-data`. This report allows the results over
 time to be visualized.
 
 The reports for the most recent test suite run against master can be found at:
@@ -37,10 +37,10 @@ The reports for the most recent test suite run against master can be found at:
 - [macOS Performance Test](https://builds.gradle.org/repository/download/Gradle_Master_Check_PerformanceTest7_Trigger/.lastFinished/performance-test-results.zip!/report/index.html)
 - [Windows Performance Test](https://builds.gradle.org/repository/download/Gradle_Master_Check_PerformanceTest6_Trigger/.lastFinished/performance-test-results.zip!/report/index.html)
 
-Running all the tests at once will be resource intensive and quite long (multiple hours).
-However, you can find instructions for running a single performance test on the top of the Graph page for each of them.
-The result of that local run will not include comparisons with previous executions, but you can then look at the numbers and verify that your changes do not introduce a regression.
+Running all the tests at once will be resource-intensive and long (multiple hours).
+However, you can find instructions for running a single performance test at the top of each Graph page.
+The result of that local run will not include comparisons with previous executions. Still, you can then look at the numbers and verify that your changes do not introduce a regression.
 
 ### Tracking down performance regressions
 
-For tracking down performance regressions see [Tracking down performance regressions with `git bisect`](docs/performance-bisect.md).
+For tracking down performance regressions, see [Tracking down performance regressions with `git bisect`](docs/performance-bisect.md).