Skip to content

Fourgate 0.4.0b1

Pre-release
Pre-release

Choose a tag to compare

@hifzabuildsai hifzabuildsai released this 31 Oct 14:11
· 4 commits to main since this release
7e64c0b

Fourgate 0.4.0b1 limited beta

0.4.0b1 is the first limited-beta package candidate after published release
0.3.0. This note prepares the release; it does not record a package upload,
tag, GitHub release, merge or deployment.

Included package paths

The package supports Python 3.10–3.13 on Linux and Windows for local,
command-configured stdio MCP workflows:

  • fourgate scan executes only explicitly contracted writes on an authorized
    disposable test account and produces opt-in JSON/HTML reports.
  • fourgate init scaffolds reviewed scan/runtime/read-back configuration without
    starting a server or contacting a target.
  • fourgate doctor performs bounded setup and discovery checks without a write
    or verifier GET.
  • fourgate guard runs the local stdio Outcome Guard in shadow or enforce mode;
    uncertainty remains UNKNOWN and fails open.
  • fourgate summary renders a local outcome log as HTML.
  • fourgate mcp provides read-only registered-workflow validation by default.
    Opt-in execution requires a separate operator policy, prepared single-use
    state and an explicit write budget.

The GitHub Issue reference pack and coding-agent setup skills remain checkout
resources. Installing the wheel does not install those skills or prove client UI
routing.

Evidence and release boundary

Product runtime behavior is unchanged from merged PR #57 and fresh main merge
commit 363bceaeb87f15df5a86db18f421d8648d73fcc5, apart from the package version
constant. Its
fixture-only CI run
passed on Linux with Python 3.10, 3.12 and 3.13 and on Windows with Python 3.12;
both package jobs and the local scan-template controls also passed. The
D4 record separately records
one bounded founder-owned hosted acceptance at the earlier pinned source. It is
historical evidence, not authorization to rerun the workflow or reuse its grant.

The retained Windows short-verifier evidence includes real process timeouts at a
500 ms fixture budget and an outer-versus-inner timeout-reason race. Test changes
made the credential-routing and reason-code oracles deterministic while keeping
UNKNOWN, wire preservation and the configured deadlines strict. They are not a
runtime timing fix
, and they do not establish that a real short verifier always
finishes within 500 ms on Windows.

The following remain unvalidated for this limited beta:

  • complete Desktop UI selection, reload and protected execution;
  • customer-owned CI and external developer onboarding;
  • production reliability, universal protocol/provider coverage and provider
    exactly-once behavior;
  • remote MCP HTTP/SSE transport.

Installation after publication

Install the exact PyPI pre-release:

python -m pip install --pre "fourgate==0.4.0b1"
python -m fourgate --version

Or install the reviewed wheel after comparing its SHA-256 with the final artifact
table below:

python -m pip install fourgate-0.4.0b1-py3-none-any.whl
python -m fourgate --version

Expected version output: fourgate 0.4.0b1.

Final artifacts

The final versioned artifacts were built once from this release-preparation
worktree with Python 3.12.14 and python -m build. The wheel was built through
the generated sdist. twine check, metadata/source inspection, fresh wheel and
direct-sdist installs, dependency checks, focused version/discovery tests and
installed-package smokes all passed.

Artifact Bytes SHA-256
fourgate-0.4.0b1-py3-none-any.whl 83,580 88701ebd9873d38d3852f21704102c8ec99e02e8ec5c467c08a0856e9668abdf
fourgate-0.4.0b1.tar.gz 144,047 052da25a37a0fb41a683b151a95be404edb9c2bbce4c2d1ac72ef7256240c931

The existing setuptools warning for the legacy TOML license table remains
non-blocking for this build. Migrate it before setuptools' stated
2027-02-18 removal deadline; no unrelated metadata migration is included here.

Publication procedure

Run these only after the release-preparation PR is approved and merged. Use the
same reviewed wheel and sdist whose hashes appear above; do not rebuild between
review and upload.

  1. Fetch main, verify it contains the approved PR and confirm its tree matches
    the reviewed release head. Stop on any mismatch.
  2. Recheck both artifact hashes and run python -m twine check on the exact two
    files.
  3. Create an annotated v0.4.0b1 tag at the verified merge commit and inspect it
    before pushing the tag.
  4. Upload the exact wheel and sdist to PyPI with authenticated Twine. PyPI
    versions and filenames are immutable; stop on uncertainty rather than
    rebuilding or retrying an ambiguous upload.
  5. Create a GitHub pre-release from the pushed tag, attach the same two files and
    use this note as the release notes.
  6. Download the published wheel by exact version in a fresh environment, verify
    its SHA-256, run python -m fourgate --version and the local bundled demo, and
    record the publication URLs. This post-publication check uses no live target.

No release step authorizes a live acceptance workflow, credential access,
customer write, grant reset, deployment or production rollout.

The exact PowerShell sequence, after substituting the approved release PR head,
is:

$fourgateApprovedHead = '<APPROVED_RELEASE_PR_HEAD>'
$fourgateReleaseRoot = Resolve-Path '.\fourgate-output\release-0.4.0b1-20261031-363bcea'
$fourgateWheel = Join-Path $fourgateReleaseRoot 'dist\fourgate-0.4.0b1-py3-none-any.whl'
$fourgateSdist = Join-Path $fourgateReleaseRoot 'dist\fourgate-0.4.0b1.tar.gz'
$fourgateBuildPython = Join-Path $fourgateReleaseRoot 'build-env\Scripts\python.exe'

git fetch --no-tags origin main
git switch main
git pull --ff-only origin main
$fourgateReleaseCommit = git rev-parse HEAD
git diff --quiet $fourgateApprovedHead $fourgateReleaseCommit
if ($LASTEXITCODE -ne 0) { throw 'Merged main tree differs from the approved release head.' }

Get-FileHash -Algorithm SHA256 -LiteralPath $fourgateWheel, $fourgateSdist
& $fourgateBuildPython -m twine check $fourgateWheel $fourgateSdist

git tag -a v0.4.0b1 $fourgateReleaseCommit -m 'Fourgate 0.4.0b1'
git show --no-patch --decorate v0.4.0b1
git push origin refs/tags/v0.4.0b1

& $fourgateBuildPython -m twine upload --repository pypi --non-interactive $fourgateWheel $fourgateSdist
gh release create v0.4.0b1 $fourgateWheel $fourgateSdist --repo hifzabuildsai/fourgate --verify-tag --prerelease --title 'Fourgate 0.4.0b1' --notes-file docs/releases/0.4.0b1.md

$fourgateVerifyRoot = Join-Path $fourgateReleaseRoot 'published-verification'
New-Item -ItemType Directory -Path $fourgateVerifyRoot
& $fourgateBuildPython -m venv (Join-Path $fourgateVerifyRoot 'venv')
$fourgateVerifyPython = Join-Path $fourgateVerifyRoot 'venv\Scripts\python.exe'
& $fourgateVerifyPython -m pip download --only-binary=:all: --no-deps --dest $fourgateVerifyRoot 'fourgate==0.4.0b1'
Get-FileHash -Algorithm SHA256 -LiteralPath (Join-Path $fourgateVerifyRoot 'fourgate-0.4.0b1-py3-none-any.whl')
& $fourgateVerifyPython -m pip install --no-index --find-links $fourgateVerifyRoot 'fourgate==0.4.0b1'
& $fourgateVerifyPython -m fourgate --version
& $fourgateVerifyPython -m fourgate demo --out (Join-Path $fourgateVerifyRoot 'demo')

Twine authentication must come from the operator's existing secure environment
or configuration; never place its value in these commands, chat, Git or process
arguments. If upload completion is uncertain, inspect the package index and
hashes before any further action. Do not rebuild or repeat an ambiguous upload.