Relay 0.0.5

Relay 0.0.5 adds optional realtime team statuses while API testing stays on your backend.

• Native Python and Node connections use three private backend environment variables.
• Verified updater names, reader/writer membership, revision acknowledgements, conflict handling and reconnect recovery.
• API execution and local notes remain usable when collaboration is offline.
• Reviewed Git-status import preserves Git files, skips existing team statuses and rejects changed previews.
• The shared service is bundled in relay-backend[realtime], with team init/add-member/serve commands. No repository clone or frontend build is needed.
• Tested in-place upgrades from Python 0.0.4 and npm 0.0.3 preserve local notes/statuses and existing integrations.

Install or upgrade:

python -m pip install --upgrade relay-backend
# Optional team collaboration / service:
python -m pip install --upgrade "relay-backend[realtime]"
# Node:
npm install relay-backend@latest

Team setup and migration · Verification

Python 3.11/3.12/3.13 and Node 22.13/24/26 compatibility CI passed before tagging. Publication workflows rerun artifact/consumer verification before registry upload. Both registries now serve 0.0.5. Fresh unpinned Python and npm installations passed their consumer checks, and a fresh public realtime installation passed the Python/Node migration, attribution, conflict, offline execution and reconnect workflow. CI-built distributions and SHA-256 checksums are attached below.

Relay v0.0.4

• Guided init commands for Python and Node: bounded framework detection, preview-first FastAPI/Express integration edits and manual guidance for ambiguous layouts.
• doctor commands with local runtime/package, OpenAPI, mount and Git configuration checks; sanitized JSON output.
• Local endpoint note editing with explicit Save/Cancel, retained unsaved edits, stale-contract review and recent endpoint activity.
• Persistent contract-change explanations identifying changed parameter/body/response/authentication sections without storing duplicate contracts or traffic.
• Separate schema/team sync feedback, schema change counts and an explicit retry for enabled Git sharing.
• Explicit named request-example loading, preserved body edits during content-type switches and accessible required-input errors.
• Exports use the endpoint's current manual status, including contract-invalidated Needs fixing.
• Bounded local activity history, additive workspace migration and protection against Node status-save/schema-refresh races.
• Windows report compatibility: restore the legacy module entry point and use the canonical module for new associations.

Realtime collaboration, multipart uploads and optional request history/assertion/export-review features remain deferred. Published on PyPI and GitHub. The verified Node 0.0.4 tarball is attached to the GitHub release; npm publication is awaiting account authentication.

Upgrade Python: pip install --upgrade relay-backend.

The November 2026 v0.0.5 roadmap targets optional authenticated realtime team statuses. See the README for milestones.

Relay 0.0.3

Relay 0.0.3 adds automatic team statuses through your backend repository's existing Git remote. Enable with install_relay(app, sync_status=True); it uses a separate status-only branch and preserves application code, staged files and request drafts. Teammates need remote read/write access.

The canonical Python import is now relay_backend; existing root relay_agent imports remain compatible. Browser titles automatically show Relay - <application title>. Bundled branding is verified against source, the favicon refreshes by package version, and unused artwork/metadata has been removed.

Fresh installation: python -m pip install relay-backend. Existing installation: python -m pip install --upgrade relay-backend, then restart the backend.

Validation: 89 Python tests, 42 frontend tests, strict build, independent wheel/assets/native checks, clean installs with current/minimum dependencies, cross-environment status tests, and Linux CI on Python 3.11/3.12/3.13. Live native integration and both endpoint exports were verified in a backend using Socket.IO.

Setup · Team statuses

Relay v0.0.2

Relay 0.0.2 improves everyday FastAPI request testing while keeping installation to one package and two lines.

python -m pip install --upgrade relay-backend==0.0.2

from relay_agent import install_relay
install_relay(app)

Restart your backend and open /relay/ on its existing port.

Changes:

• Repeated array query parameters, optional bodies and consistent header validation.
• Accurate auth feedback and independent shared/endpoint credentials.
• Exact JSON numeric formatting, preserved previous responses and explicit empty/truncated response handling.
• Refined Relay branding and custom illustrated setup guides.
• Runnable factory/router example with separate user/admin demo auth.

Validation: 82 Python tests, 40 frontend tests, production build, current/minimum dependency clean installs, Socket.IO integration and browser copy/export flows. Linux CI passed on Python 3.11, 3.12 and 3.13. The release workflow completed successfully. A fresh install of the published PyPI package verified native discovery, user/admin auth, request execution, nested/optional bodies, query arrays, validation and empty responses.

Setup guide | Testing guide | Changelog

Python 3.11+. Local development alpha; multipart and OAuth browser flows remain outside this release.

Relay v0.0.1

Relay 0.0.1 is the first Apache-2.0 alpha release.

python -m pip install relay-backend==0.0.1

from relay_agent import install_relay
install_relay(app)

Start your backend normally and open /relay on its existing port. The package includes the UI, fonts and assets; no clone, frontend build or companion process is required.

Includes categorized API testing, shared/per-endpoint auth, response inspection, manual statuses with Git attribution, themes, and .relay/JSON exports. Python 3.11+ is required.

Documentation · Changelog

Published on PyPI. Public installation, bundled UI/assets and native API execution were verified in a fresh environment. See the documentation for supported local-development workflows and alpha limitations.