You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Deploy the Skra ports (PR #1) together with the workflow authorization fix #3
How Bifrost updates a Git-connected install (verified in platform main source): every 6 hours it reads version: from bifrost.solution.yaml at the connected ref's latest commit. Git tags and GitHub Releases are not used. If that version is newer, it badges the install and emits solution.update_available. Nothing applies the update except a sync (bifrost solution sync or POST /api/solutions/{id}/sync).
Conventions for this repo:
Version every deployable change on mtg with a PEP 440 local label: 0.1.3+mtg.1, 0.1.3+mtg.2, … When upstream releases 0.1.4, merge it and continue with 0.1.4+mtg.1. I verified the ordering with the same packaging library the platform uses: 0.1.3 < 0.1.3+mtg.1 < 0.1.3+mtg.2 < 0.1.4. CI enforces the bump on PRs into mtg.
Merging to mtg deploys. The Solution GitOps controller (being built) receives the GitHub push webhook and syncs installs that follow mtg. Subscribing to solution.update_available gives a 6-hourly reconcile backstop. Until the controller is live, run bifrost solution sync bifrost-docs after merging.
mtg is branch-protected: PR plus green CI required.
PR #1 gets version: 0.1.3+mtg.1 once the #4 test fix lands, and still waits for #2.
The Solution GitOps controller is live in production (Midtown-Technology-Group/bifrost-solution-gitops). This repo has a push webhook to it, verified end to end on the controller's own repo: merge → webhook → sync → new version installed.
Activity
MTG-Thomas commentedon Nov 16, 2026
Update: GitOps release flow (decided 2026-11-16)
How Bifrost updates a Git-connected install (verified in platform
mainsource): every 6 hours it readsversion:frombifrost.solution.yamlat the connected ref's latest commit. Git tags and GitHub Releases are not used. If that version is newer, it badges the install and emitssolution.update_available. Nothing applies the update except a sync (bifrost solution syncorPOST /api/solutions/{id}/sync).Conventions for this repo:
mtgwith a PEP 440 local label:0.1.3+mtg.1,0.1.3+mtg.2, … When upstream releases0.1.4, merge it and continue with0.1.4+mtg.1. I verified the ordering with the samepackaginglibrary the platform uses:0.1.3 < 0.1.3+mtg.1 < 0.1.3+mtg.2 < 0.1.4. CI enforces the bump on PRs intomtg.mtgdeploys. The Solution GitOps controller (being built) receives the GitHub push webhook and syncs installs that followmtg. Subscribing tosolution.update_availablegives a 6-hourly reconcile backstop. Until the controller is live, runbifrost solution sync bifrost-docsafter merging.mtgis branch-protected: PR plus green CI required.PR #1 gets
version: 0.1.3+mtg.1once the #4 test fix lands, and still waits for #2.MTG-Thomas commentedon Nov 16, 2026
GitOps status (2026-11-16):
mtghas CI (CI: test against production SDKs, enforce version bumps, fix test tooling (#4) #27) and is protected: PR required;python-tests,app-testsandversion-policyrequired.notifyin the controller policy. Merging policy: deploy Bifrost Docs on merge to mtg bifrost-solution-gitops#3 (draft) switches Docs to deploy-on-merge.0.1.3+mtg.1and green, and stays on hold for Security hardening for Solution workflows (tracked privately) #2.Remaining in this issue: merge #2's fix plus #1, opt in via the controller PR, and smoke-test as a non-admin Reader.