Server status ...

magogi/prod/: mgf-fed-0.2.0 metadata and description

Simple index Newer version available

Magogi Foundation federation orchestrator — runs the recurring cross-repo work (gates, local/remote release, status) consistently and trackably over the mgf-* fleet.

author mgf-fed contributors
description_content_type text/markdown
license MIT
license_file
  • LICENSE
metadata_version 2.4
project_urls
  • Homepage, https://codeberg.org/magogi-admin/mgf-fed
  • Issues, https://codeberg.org/magogi-admin/mgf-fed/issues
requires_dist
  • import-linter>=2; extra == 'dev'
  • mypy>=1.8; extra == 'dev'
  • pytest-cov>=5; extra == 'dev'
  • pytest-timeout<3,>=2.3; extra == 'dev'
  • pytest>=8.0; extra == 'dev'
  • ruff<0.16,>=0.4; extra == 'dev'
  • mgf-common[standards]<0.47,>=0.46; extra == 'standards'
  • mgf-test-supervisor<0.2,>=0.1; extra == 'supervisor'
requires_python >=3.11

Because this project isn't in the mirror_whitelist, no releases from root/pypi are included.

File Tox results History
mgf_fed-0.2.0-py3-none-any.whl
Size
23 KB
Type
Python Wheel
Python
3

mgf-fed — Magogi Foundation federation orchestrator

Runs the recurring cross-repo work — quality gates, local/remote release, status — consistently, controllably, and trackably across the mgf-* fleet, in dependency-wave order. It composes existing assets rather than reinventing them:

Concern Reused asset
release/build order mgf-standard registry (MGF_LIBRARIES.json → release_waves)
gate/test runner mgf-test-supervisor (mtest)
local CI woodpecker-cli exec (the real .woodpecker pipeline, in containers)
SCM/release flow tea + git, with the federation guardrails baked in

Plan & rationale: see mgf-standard/docs/inprogress/federation-automation-and-release-plan.md.

Status (Phase 0)

Read-only tracker only:

mgf-fed status              # the federation matrix (version, conformance %, scaffolding)
mgf-fed status --json       # machine-readable -> ~/.mgf/MGF_FED_STATUS.json
mgf-fed status --shape python

Set MGF_ROOT if the sibling repos aren't under ~/PycharmProjects.

Later phases (stubbed in --help): gates, local-ci, release-local, release-remote, scaffold, drift-check, registry.