## 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

 * 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">

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"

object StartReleaseCycleTest : BasePromotionBuildType(cleanCheckout = false) {
    init {
        id("Promotion_AllBranchesStartReleaseCycleTest")
        name = "Start Release Cycle Test"
        description = "Test for Start Release Cycle pipeline"

        steps {
            gradleWrapper {
                name = "PromoteTest"
                tasks = "clean promoteStartReleaseCycle"

# See https://developer.nvidia.com/cuda-gpus#compute
# `compute_XY` enables PTX embedding in addition to SASS. PTX
# is forward compatible beyond the current compute capability major
# release while SASS is only forward compatible inside the current
# major release. Example: sm_80 kernels can run on sm_89 GPUs but
# not on sm_90 GPUs. compute_80 kernels though can also run on sm_90 GPUs.

            <p>See the <a href="https://bt-internal-docs.grdev.net/gbt/how-to/release/release-troubleshooting/#binary-compatibility-check-failed-">documentation</a> for more details.</p>
            <p>
            We check the binary compatibility by comparing the current code’s binary interfaces
            against THE LATEST VERSION WHICH IS RELEASED FROM RELEASE BRANCH (from `released-version.json` on this branch)

Documentation = "https://fastapi.tiangolo.com/"
Repository = "https://github.com/fastapi/fastapi"
Issues = "https://github.com/fastapi/fastapi/issues"
Changelog = "https://fastapi.tiangolo.com/release-notes/"

[project.optional-dependencies]

standard = [
    "fastapi-cli[standard] >=0.0.8",
    # For the test client
    "httpx >=0.23.0,<1.0.0",
    # For templates
    "jinja2 >=3.1.5",

 * limitations under the License.
 */

class VersionedSettingsBranchTest {
    @ParameterizedTest
    @CsvSource(
        value = [
            "master,    0",
            "release,   1",
            "release6x, 2",
            "release7x, 3",
            "release27x,23",
        ],
    )
    fun branchesWithVcsTriggerEnabled(
        branchName: String,

        env:
          GITHUB_CONTEXT: ${{ toJson(github) }}
        run: echo "$GITHUB_CONTEXT"
      - name: Decide whether the needed jobs succeeded or failed
        uses: re-actors/alls-green@release/v1
        with: