Signed-off-by: bot-teamcity <bot-teamcity@gradle.com>

If we don't, then the invariant that all queued work is processed by the
main thread before `waitForWorkToComplete` can be violated.

Fixes gradle/gradle-private#5272

Turn preparePatchRelease into a logic-free lifecycle task that wires
together the individual steps of preparing a patch release, so the
release notes are prepared as part of the same command.

The version-bump logic moves to a new bumpVersionForPatchRelease task
(renamed from the former PreparePatchRelease) which bumps version.txt
and records the just-released version in released-versions.json.

A new preparePatchReleaseNotes task rewrites the release notes intro
into the patch-release format, laying down the "fixed issues" marker
and placeholder so updateFixedIssuesInReleaseNotes can populate it
afterwards.

Order matters: preparePatchReleaseNotes reads version.txt and must run
after the bump, otherwise it would record the wrong version. This is
enforced with mustRunAfter, and the task reads version.txt at execution
time rather than configuration time.

…pe (#38292)

…8272)

…recation

The deprecation of Task.taskDependencies at execution time (introduced in
9.6.0-M2 by 8b39d9a) was handled in the forward compatibility spec
(0af1826) but the backwards compatibility spec was missed.

Signed-off-by: Christoph Obexer <cobexer@gradle.com>

The --non-interactive flag shipped in 9.6.0 with no Gradle property.
It was also a negative-only flag, inconsistent with Gradle's
positive-flag + --no- convention.

Since the feature is incubating, reshape it: add --interactive and
--no-interactive backed by the org.gradle.console.interactive property,
and drop --non-interactive. Rename the incubating LoggingConfiguration
and StartParameter API from isNonInteractive/setNonInteractive to
isInteractive/setInteractive.

PR #38301 introduced --interactive/--no-interactive to toggle interactive
console prompting. Following review, restore the original --non-interactive
flag (shipped in 9.6.0), now marked incubating, and drop the newly added
--interactive/--no-interactive flags.

The org.gradle.console.interactive Gradle property (true/false) remains as the
property-based control, and the incubating isInteractive/setInteractive API is
unchanged.

)

…ive (#38303)