Rollout: scheduled release and automatic promote #5

Open
opened 2026-11-10 22:25:05 +01:00 by robin.wieske · 2 comments
Owner

Context

Tracking issue for scheduled releases and automatic promote to prod across all repos in scope. Work top to bottom; an item can start once its blockers are closed.

Plan: https://forgejo.entwirr.me/Wi3eDigital/laravel-deploy-actions/src/branch/main/docs/plan.md (plan PR: #1)

To continue in a Claude session: "continue the deploy rollout" (read this issue, work on what is unblocked).

Rollout

  1. Security
  2. Shared actions and notifications (this repo)
    • #2 release-gate action. Blocked by: plan PR #1
    • #3 env-diff, verify-deploy and notify actions. Blocked by: plan PR #1
    • #4 n8n "Deploy notify" workflow and heartbeat. Blocked by: n8n header credential (owner)
  3. Pilot
  4. Remaining repos
  5. Deferred (label blocked)

Owner checklist

  • Rotate the homepage Ploi deploy token
  • Rotate RELEASE_DRAFTER_TOKEN
  • Create the release bot user and RELEASE_BOT_TOKEN (scopes write:repository + read:issue, 90-day expiry) in each repo
  • Create the n8n header auth credential for "Deploy notify" (X-Notify-Token) and set DEPLOY_NOTIFY_URL / DEPLOY_NOTIFY_TOKEN secrets
  • Add the pre-deploy backup block to each prod Ploi deploy script (docs/predeploy-backup.md): aevana, slight-exposure, kima/portal, kima/kima (if applicable), homepage; Kardeema once prod exists
  • One test restore per repo, date noted in the repo issue

Acceptance criteria

  • Every item above is closed or still carries blocked with its unblock condition
  • Every repo in scope has the milestone "Auto release & promote"
  • Every repo in scope sends heartbeat and shows up in the n8n weekly summary as reporting
## Context Tracking issue for scheduled releases and automatic promote to prod across all repos in scope. Work top to bottom; an item can start once its blockers are closed. Plan: https://forgejo.entwirr.me/Wi3eDigital/laravel-deploy-actions/src/branch/main/docs/plan.md (plan PR: https://forgejo.entwirr.me/Wi3eDigital/laravel-deploy-actions/pulls/1) To continue in a Claude session: "continue the deploy rollout" (read this issue, work on what is unblocked). ## Rollout 1. Security - [ ] Security: drafter debug print https://forgejo.entwirr.me/Wi3eDigital/forgejo-release-drafter-action/pulls/61, homepage webhook secret https://forgejo.entwirr.me/Wi3eDigital/homepage/pulls/305, token rotation (owner). Blocked by: nothing 2. Shared actions and notifications (this repo) - [ ] https://forgejo.entwirr.me/Wi3eDigital/laravel-deploy-actions/issues/2 release-gate action. Blocked by: plan PR #1 - [ ] https://forgejo.entwirr.me/Wi3eDigital/laravel-deploy-actions/issues/3 env-diff, verify-deploy and notify actions. Blocked by: plan PR #1 - [ ] https://forgejo.entwirr.me/Wi3eDigital/laravel-deploy-actions/issues/4 n8n "Deploy notify" workflow and heartbeat. Blocked by: n8n header credential (owner) 3. Pilot - [ ] https://forgejo.entwirr.me/Aevana/aevana/issues/2021 Aevana pilot, `AUTO_PROMOTE=dry-run` for 1 to 2 weeks, then `on`. Blocked by: #2, #3, #4 4. Remaining repos - [ ] https://forgejo.entwirr.me/slight-exposure/slight-exposure/issues/3952 slight-exposure. Blocked by: Aevana/aevana#2021, #2, #3 - [ ] https://forgejo.entwirr.me/kima/portal/issues/111 kima/portal. Blocked by: Aevana/aevana#2021 - [ ] https://forgejo.entwirr.me/kima/kima/issues/206 kima/kima via desktop beta channel. Blocked by: kima/portal#111, #2 - [ ] https://forgejo.entwirr.me/Kardeema/kardeema/issues/2214 Kardeema scheduled release (staging only). Blocked by: Aevana/aevana#2021 - [ ] https://forgejo.entwirr.me/Wi3eDigital/homepage/issues/306 homepage straight to prod. Blocked by: #2, #3 and the homepage security PR 5. Deferred (label `blocked`) - [ ] https://forgejo.entwirr.me/kima/kima/issues/207 kima web staging site. Blocked by: a staging Ploi site exists - [ ] https://forgejo.entwirr.me/Kardeema/kardeema/issues/2215 Kardeema automatic promote to prod. Blocked by: a prod environment exists ## Owner checklist - [ ] Rotate the homepage Ploi deploy token - [ ] Rotate `RELEASE_DRAFTER_TOKEN` - [ ] Create the release bot user and `RELEASE_BOT_TOKEN` (scopes `write:repository` + `read:issue`, 90-day expiry) in each repo - [ ] Create the n8n header auth credential for "Deploy notify" (`X-Notify-Token`) and set `DEPLOY_NOTIFY_URL` / `DEPLOY_NOTIFY_TOKEN` secrets - [ ] Add the pre-deploy backup block to each prod Ploi deploy script (`docs/predeploy-backup.md`): aevana, slight-exposure, kima/portal, kima/kima (if applicable), homepage; Kardeema once prod exists - [ ] One test restore per repo, date noted in the repo issue ## Acceptance criteria - [ ] Every item above is closed or still carries `blocked` with its unblock condition - [ ] Every repo in scope has the milestone "Auto release & promote" - [ ] Every repo in scope sends `heartbeat` and shows up in the n8n weekly summary as reporting
Author
Owner

Status 2026-11-11 (overnight run)

Merged (all inert: DEPLOYS_ENABLED=false, AUTO_RELEASE=off, AUTO_PROMOTE=off in every repo):

  • Shared actions: plan #1, env-diff/verify-deploy/notify #6, release-gate #7 (main 2d80ae1e). CI retry fix #8 closed.
  • Drafter token print removed: Wi3eDigital/forgejo-release-drafter-action#61.
  • Off switches: Aevana#2022, slight-exposure#3953, kima/portal#112, Kardeema#2216, kima/kima#208 (+ bench sharding #209).
  • Rollout: Aevana#2023 (+ #2024), slight-exposure#3955 (+ #3956), kima/portal#114 (+ #115), Kardeema#2218, kima/kima#210.
  • n8n "Deploy notify" (d9Tw3FIqnGOjfvG0) and "heartbeat check" (DQvPEV7oHPAgpdmv) built, unpublished (#4).

Open:

  • Wi3eDigital/homepage#305 (webhook secret, off switch, CI image) and #307 (rollout, on top of #305). CI red until the livewire/flux-pro 2.11.1 lock is bumped (404 in the registry). Homepage deploys are NOT switched off until #305 merges.

Issues found on the way:

  • kima/kima: bench still exceeds 600 s when two bench jobs share the runner (runner setup decision).
  • kima/desktop-updates feed returns 404 anonymously (org kima is private): installed desktop clients probably cannot download updates.
  • kima/portal prod /version reports dev, so kima promote fails until portal prod runs a tagged release.
  • Aevana#2025: date-boundary flaky test.

Issues #2021, #3952, #111, #2214, #206, #306 stay open for the dry-run period.

## Status 2026-11-11 (overnight run) Merged (all inert: `DEPLOYS_ENABLED=false`, `AUTO_RELEASE=off`, `AUTO_PROMOTE=off` in every repo): - Shared actions: plan #1, env-diff/verify-deploy/notify #6, release-gate #7 (main `2d80ae1e`). CI retry fix #8 closed. - Drafter token print removed: Wi3eDigital/forgejo-release-drafter-action#61. - Off switches: Aevana#2022, slight-exposure#3953, kima/portal#112, Kardeema#2216, kima/kima#208 (+ bench sharding #209). - Rollout: Aevana#2023 (+ #2024), slight-exposure#3955 (+ #3956), kima/portal#114 (+ #115), Kardeema#2218, kima/kima#210. - n8n "Deploy notify" (d9Tw3FIqnGOjfvG0) and "heartbeat check" (DQvPEV7oHPAgpdmv) built, unpublished (#4). Open: - Wi3eDigital/homepage#305 (webhook secret, off switch, CI image) and #307 (rollout, on top of #305). CI red until the `livewire/flux-pro` 2.11.1 lock is bumped (404 in the registry). Homepage deploys are NOT switched off until #305 merges. Issues found on the way: - kima/kima: bench still exceeds 600 s when two bench jobs share the runner (runner setup decision). - kima/desktop-updates feed returns 404 anonymously (org `kima` is private): installed desktop clients probably cannot download updates. - kima/portal prod `/version` reports `dev`, so kima promote fails until portal prod runs a tagged release. - Aevana#2025: date-boundary flaky test. Issues #2021, #3952, #111, #2214, #206, #306 stay open for the dry-run period.
Author
Owner

Update 2026-11-11 morning: homepage #305 + #307 merged (flux/flux-pro 2.21.0, livewire 4.4.8, pnpm 11 allowBuilds, approved by owner); homepage deploys now behind DEPLOYS_ENABLED. Aevana promote moved to 07:05 UTC (Aevana/aevana#2028). Today's scheduled Publish Release runs (aevana, slight-exposure, portal, kardeema, kima) all succeeded with AUTO_RELEASE=off, so the cross-repo uses: resolved. Remaining: owner checklist above.

Update 2026-11-11 morning: homepage #305 + #307 merged (flux/flux-pro 2.21.0, livewire 4.4.8, pnpm 11 `allowBuilds`, approved by owner); homepage deploys now behind `DEPLOYS_ENABLED`. Aevana promote moved to 07:05 UTC (Aevana/aevana#2028). Today's scheduled Publish Release runs (aevana, slight-exposure, portal, kardeema, kima) all succeeded with `AUTO_RELEASE=off`, so the cross-repo `uses:` resolved. Remaining: owner checklist above.
Sign in to join this conversation.
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Wi3eDigital/laravel-deploy-actions#5
No description provided.