Light, fluffy, and always free - The AWS Local Emulator alternative
ci: cut a release at 00:30 Central on the 15th and last day of the month (#5698)
Hector Venturacb58b12b4166
diff --git a/.github/workflows/release-cut.yml b/.github/workflows/release-cut.ymlindex 97ea790008..1d09af621c 100644--- a/.github/workflows/release-cut.yml+++ b/.github/workflows/release-cut.yml@@ -2,7 +2,7 @@ name: Release Cut# One-button release from main.#-# Manually dispatched: semantic-release analyzes the Conventional Commits on+# On dispatch or cron: semantic-release analyzes the Conventional Commits on# main, bumps pom.xml (via the exec plugin running `mvn versions:set`), writes# CHANGELOG.md, commits those files, tags the release (tagFormat: ${version}),# and creates the GitHub Release. The tag push then fires release.yml exactly@@ -22,6 +22,12 @@ name: Release Cut# Required secrets: GH_TOKENon:+ # 00:30 America/Chicago on the 15th and on the last day of the month.+ # GitHub applies the timezone, DST included. Cron cannot express "last day+ # of the month", so it fires on 28-31 and the gate job keeps the real one.+ schedule:+ - cron: '30 0 15,28-31 * *'+ timezone: America/Chicagoworkflow_dispatch:inputs:dry-run:@@ -32,19 +38,44 @@ on:permissions:contents: write-# Serialize release cuts: a second dispatch queues behind the first instead of-# racing it to the same version/tag. No cancel-in-progress — never kill a-# mid-flight release. GitHub keeps at most ONE pending run per group, so if-# several dispatches pile up, only the latest pending one runs — intentional:-# duplicate queued release cuts are redundant by definition (the surviving run-# re-analyzes main and releases whatever is unreleased).-concurrency:- group: release-cut-jobs:+ gate:+ name: Check release window+ runs-on: ubuntu-latest+ permissions: {}+ outputs:+ cut: ${{ steps.window.outputs.cut }}+ steps:+ - id: window+ env:+ EVENT: ${{ github.event_name }}+ run: |+ if [ "$EVENT" = "workflow_dispatch" ]; then+ echo "cut=true" >> "$GITHUB_OUTPUT"; exit 0+ fi+ export TZ=America/Chicago+ if [ "$(date +%d)" = "15" ] || [ "$(date -d tomorrow +%d)" = "01" ]; then+ echo "cut=true" >> "$GITHUB_OUTPUT"+ else+ echo "$(date +%F) is neither the 15th nor the last day of the month; skipping."+ fi+release:name: Cut release from main+ needs: gate+ if: needs.gate.outputs.cut == 'true'runs-on: ubuntu-latest+ # Serialize release cuts: a second dispatch queues behind the first instead+ # of racing it to the same version/tag. No cancel-in-progress — never kill a+ # mid-flight release. GitHub keeps at most ONE pending run per group, so if+ # several dispatches pile up, only the latest pending one runs —+ # intentional: duplicate queued release cuts are redundant by definition+ # (the surviving run re-analyzes main and releases whatever is unreleased).+ #+ # Job-level, not workflow-level, so the scheduled runs the gate skips+ # never take or replace the one pending slot in this group.+ concurrency:+ group: release-cut# semantic-release comments on and labels every issue and PR in the release,# which is roughly two API writes each. A 278-PR release took ~22 minutes.timeout-minutes: 60diff --git a/CONTRIBUTING.md b/CONTRIBUTING.mdindex 4471ec1bd8..656644bc19 100644--- a/CONTRIBUTING.md+++ b/CONTRIBUTING.md@@ -55,7 +55,7 @@ suites in Docker against it.## Branching Model-Floci uses a **tag-driven release model**. Merging a PR never publishes a release image. `main` is published once a day as the `nightly` channel, and a stable release is published only when a maintainer runs the "Release Cut" workflow (`.github/workflows/release-cut.yml`, `workflow_dispatch`). That workflow runs semantic-release, which bumps `pom.xml`, writes `CHANGELOG.md`, commits, and pushes the `X.Y.Z` tag. The tag then triggers `.github/workflows/release.yml`, which builds and publishes the release images to Docker Hub and public ECR.+Floci uses a **tag-driven release model**. Merging a PR never publishes a release image. `main` is published once a day as the `nightly` channel, and a stable release is published only when the "Release Cut" workflow (`.github/workflows/release-cut.yml`) runs: on its schedule at 00:30 US Central time on the 15th and the last day of each month, or when a maintainer dispatches it. That workflow runs semantic-release, which bumps `pom.xml`, writes `CHANGELOG.md`, commits, and pushes the `X.Y.Z` tag. The tag then triggers `.github/workflows/release.yml`, which builds and publishes the release images to Docker Hub and public ECR.| Branch / tag | Purpose | Docker published? ||---|---|---|@@ -277,11 +277,12 @@ Once your current pull requests are reviewed, merged, or closed, you are welcome## Release Process (maintainers)-Stable releases ship on the **1st and 3rd Tuesday of each month**. Merging to `main` does-not cut a release: the change rides the next train, and reaches the `nightly` image on the-next nightly build.+Stable releases ship on the **15th and the last day of each month**. Merging to `main`+does not cut a release: the change rides the next train, and reaches the `nightly` image on+the next nightly build.-Releases are cut from `main` with the **Release Cut** workflow+Releases are cut from `main` by the **Release Cut** workflow, which runs on a schedule at+00:30 US Central time (America/Chicago) on those days. Maintainers can also run it by hand(Actions → Release Cut → Run workflow). semantic-release analyzes theConventional Commits since the last tag, bumps `pom.xml`, regenerates`CHANGELOG.md`, commits, tags, and publishes the GitHub Release; the tagdiff --git a/README.md b/README.mdindex c92bcca424..f64a4133ab 100644--- a/README.md+++ b/README.md@@ -844,7 +844,7 @@ image: floci/floci:nightly### Release train-Stable releases ship on the **1st and 3rd Tuesday of each month**. Between trains, `floci/floci:nightly` tracks `main`. Every merged fix is available the next day, and dated `nightly-mmddyyyy` tags let you pin a specific night's build.+Stable releases ship on the **15th and the last day of each month**, cut automatically at 00:30 US Central time. Between trains, `floci/floci:nightly` tracks `main`. Every merged fix is available the next day, and dated `nightly-mmddyyyy` tags let you pin a specific night's build.Versions are derived from Conventional Commits by [semantic-release](https://github.com/semantic-release/semantic-release); `CHANGELOG.md` is generated, never hand-edited. Releases are cut from `main` only: there are no maintenance branches.diff --git a/docs/configuration/docker-images.md b/docs/configuration/docker-images.mdindex 6c8c121f25..7fb896c40a 100644--- a/docs/configuration/docker-images.md+++ b/docs/configuration/docker-images.md@@ -20,7 +20,7 @@ The standard image is built on Red Hat UBI 9 micro. Besides Floci it contains on| Channel | Source | Published ||---|---|---|-| **Release** | Tagged version (e.g. `x.y.z`) | 1st and 3rd Tuesday of each month |+| **Release** | Tagged version (e.g. `x.y.z`) | 15th and last day of each month, 00:30 CT || **Nightly** | Tip of `main` | Every night at 23:00 CT |Release images are stable and recommended for most use cases. Between trains, `nightly` carries every merged fix from the following morning. Nightly images track active development and may include unreleased changes.diff --git a/docs/contributing.md b/docs/contributing.mdindex 90c0fe9597..a9ab7afea8 100644--- a/docs/contributing.md+++ b/docs/contributing.md@@ -126,9 +126,9 @@ Please keep **no more than 4 open pull requests**, drafts included, and **no mor## Releases-Stable releases ship on the **1st and 3rd Tuesday of each month**. Merging to `main` does not cut a release: the change rides the next train, and reaches the `nightly` image on the next nightly build.+Stable releases ship on the **15th and the last day of each month**. Merging to `main` does not cut a release: the change rides the next train, and reaches the `nightly` image on the next nightly build.-Maintainers cut releases from `main` with the Release Cut workflow, which runs semantic-release over the Conventional Commits since the last tag. That is why the commit type matters: `feat:` and `fix:` move the version, `docs:` and `chore:` do not. `CHANGELOG.md` is generated from those messages and is not edited by hand; a genuine correction goes in a PR carrying the `changelog-edit` label.+Releases are cut from `main` by the Release Cut workflow, scheduled at 00:30 US Central time on those days (maintainers can also run it by hand). It runs semantic-release over the Conventional Commits since the last tag. That is why the commit type matters: `feat:` and `fix:` move the version, `docs:` and `chore:` do not. `CHANGELOG.md` is generated from those messages and is not edited by hand; a genuine correction goes in a PR carrying the `changelog-edit` label.## Reporting Security Issues