## 0.112.4

This release is mainly a big internal refactor to enable adding support for Pydantic models for `Form` fields, but that feature comes in the next release.

This release shouldn't affect apps using FastAPI in any way. You don't even have to upgrade to this version yet. It's just a checkpoint. 🤓

### Refactors

# Usage: Go to
# https://github.com/tensorflow/tensorflow/actions/workflows/release-branch-cherrypick.yml
# and click "Run Workflow." Leave "Use Workflow From" set to "master", then
# input the branch name and paste the cherry-pick commit and click Run. A PR
# will be created.

name: Release Branch Cherrypick
on:
  workflow_dispatch:
    inputs:

 * we run each branch on different hours.
 * master - 0:00
 * release - 1:00
 * release6x - 2:00
 * release7x - 3:00
 * ...
 * releaseNx - (N-4):00
 */
fun VersionedSettingsBranch.determineNightlyPromotionTriggerHour(): Int? {
    val oldReleasePattern = "release(\\d+)x".toRegex()
    return when (branchName) {
        "master" -> 0
        "release" -> 1
        else -> {

                <p>
                If change was made on the `release` branch but hasn't yet been merged to `master`, merge `release` to `master`:
                <a class="btn btn-info" role="button" data-toggle="collapse" href="#merge-release-${changeId}" aria-expanded="false" aria-controls="collapseExample">Merge release to master</a>
                <div class="collapse" id="merge-release-${changeId}">
                  <div class="well">

	<property name="maven.release.repo.url" value="https://maven.codelibs.org" />
	<property name="opensearch.version" value="3.4.0" />

	<target name="install.modules">
		<mkdir dir="${target.dir}" />
		<delete dir="${modules.dir}" />
		<mkdir dir="${modules.dir}" />

		<!-- analysis-common -->
		<antcall target="install.module">
			<param name="repo.url" value="${maven.release.repo.url}" />

Releasing
=========

1. Update `CHANGELOG.md`.

2. Set versions:

    ```
    export RELEASE_VERSION=X.Y.Z
    export NEXT_VERSION=X.Y.Z-SNAPSHOT
    ```

3. Update versions, tag the release, and prepare for the next release.

    ```
    sed -i "" \
      "s/version = \".*\"/version = \"$RELEASE_VERSION\"/g" \
      build.gradle.kts
    sed -i "" \

	<property name="maven.release.repo.url" value="https://repo1.maven.org/maven2" />

	<target name="install.plugins">
		<mkdir dir="${target.dir}" />
		<delete dir="${plugins.dir}" />
		<mkdir dir="${plugins.dir}" />
		<!-- analysis-extension -->
		<antcall target="install.plugin">
			<param name="repo.url" value="${maven.release.repo.url}" />

data class VersionedSettingsBranch(
    val branchName: String,
) {
    companion object {
        private const val MASTER_BRANCH = "master"

        private const val RELEASE_BRANCH = "release"

        private const val EXPERIMENTAL_BRANCH = "xperimental"

        // master branch of gradle/gradle-promote
        private const val GRADLE_PROMOTE_MASTER_VCS_ROOT_ID = "Gradle_GradlePromoteMaster"

    `HttpLoggingInterceptor` write to logcat by default.

The rest of this release is our highest-quality release yet. Though we continue to use the word
_alpha_ in the version name, the only unstable thing in it is some non-final APIs tagged
`@ExperimentalOkHttpApi`. You can safely use this release in production.

 *  Fix: Attempt to read the response even if sending the request failed. This makes it possible

     * This controls whether to search in release repositories, snapshot repositories, or both.
     *
     * @since 4.0.0
     */
    enum Nature {
        /**
         * Query only release repositories to discover versions.
         */
        RELEASE,
        /**
         * Query only snapshot repositories to discover versions.
         */
        SNAPSHOT,