Skip to content

ci(release): add workflow_dispatch — enable manual image builds - #257

Merged
izzywdev merged 2 commits into
masterfrom
fix/release-workflow-dispatch
Jul 15, 2026
Merged

ci(release): add workflow_dispatch — enable manual image builds#257
izzywdev merged 2 commits into
masterfrom
fix/release-workflow-dispatch

Conversation

@izzywdev

Copy link
Copy Markdown
Owner

Why

Auto-merged PRs push to master under GITHUB_TOKEN, and GitHub does not start push-triggered workflows for GITHUB_TOKEN pushes. So release.yml never ran after #247/#253/#256 — the security-service/frontend images were never built and the values tags never bumped (prod stuck on the old image).

What

Adds workflow_dispatch to release.yml → a reliable manual build+GitOps-bump path. Dispatch it after a deploy-window merge to build images + bump the 5 anchor tags (Argo then rolls out).

Durable follow-up (separate): switch auto-merge.yml to merge under a PAT/App token (needs a RELEASE_PAT secret) so normal merges trigger release again.

🤖 Generated with Claude Code

fuzeone-bot Bot and others added 2 commits July 15, 2026 11:07
…C (prod outage)

#247's reverse-proxy stripped /api/auth/idp and relied on X-Forwarded-Prefix,
but Authentik IGNORES it — so discovery advertised app.fuzefront.com/application/o/authorize/
(no prefix), an unrouted path → the browser authorize redirect 404'd → prod login broke.

Fix: route Authentik's native root paths (/application,/if,/source,/flows,/ws,/-,
/outpost.goauthentik.io,/static/dist,/static/authentik) straight to authentik-server
under app.fuzefront.com (no strip); issuer -> https://app.fuzefront.com/application/o/fuzefront/.
Boundary intact: browser stays on app.fuzefront.com, never sees the IdP host.
Chart-only — deploys via Argo, no image build. helm template renders clean.

Co-Authored-By: Claude claude-opus-4-8 <noreply@anthropic.com>
Claude-Session-Id: cf830721-b1ef-4fe0-a024-035ad280dcf7
Auto-merged PRs push to master under GITHUB_TOKEN, which GitHub does not let
trigger push-workflows — so release.yml never ran after #247/#253/#256 and the
security-service/frontend images never built. workflow_dispatch gives a reliable
manual build+GitOps-bump path (durable fix: switch auto-merge to a PAT — needs a
RELEASE_PAT secret, tracked separately).

Co-Authored-By: Claude claude-opus-4-8 <noreply@anthropic.com>
Claude-Session-Id: cf830721-b1ef-4fe0-a024-035ad280dcf7
@izzywdev izzywdev added the auto-merge Enable squash auto-merge once CI passes label Jul 15, 2026
@izzywdev
izzywdev merged commit 077f17d into master Jul 15, 2026
32 of 33 checks passed
@izzywdev
izzywdev deleted the fix/release-workflow-dispatch branch July 15, 2026 10:54
@izzywdev
izzywdev restored the fix/release-workflow-dispatch branch July 27, 2026 11:47
@izzywdev
izzywdev deleted the fix/release-workflow-dispatch branch July 27, 2026 18:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-merge Enable squash auto-merge once CI passes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant