Rollout: scheduled release and automatic promote #5
Labels
No labels
auto-update
blocked
dependency
major
release-blocker
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Wi3eDigital/laravel-deploy-actions#5
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
AUTO_PROMOTE=dry-runfor 1 to 2 weeks, thenon. Blocked by: #2, #3, #4blocked)Owner checklist
RELEASE_DRAFTER_TOKENRELEASE_BOT_TOKEN(scopeswrite:repository+read:issue, 90-day expiry) in each repoX-Notify-Token) and setDEPLOY_NOTIFY_URL/DEPLOY_NOTIFY_TOKENsecretsdocs/predeploy-backup.md): aevana, slight-exposure, kima/portal, kima/kima (if applicable), homepage; Kardeema once prod existsAcceptance criteria
blockedwith its unblock conditionheartbeatand shows up in the n8n weekly summary as reportingStatus 2026-11-11 (overnight run)
Merged (all inert:
DEPLOYS_ENABLED=false,AUTO_RELEASE=off,AUTO_PROMOTE=offin every repo):2d80ae1e). CI retry fix #8 closed.Open:
livewire/flux-pro2.11.1 lock is bumped (404 in the registry). Homepage deploys are NOT switched off until #305 merges.Issues found on the way:
kimais private): installed desktop clients probably cannot download updates./versionreportsdev, so kima promote fails until portal prod runs a tagged release.Issues #2021, #3952, #111, #2214, #206, #306 stay open for the dry-run period.
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 behindDEPLOYS_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 withAUTO_RELEASE=off, so the cross-repouses:resolved. Remaining: owner checklist above.