Skip to content

Validate and release the forge

The Check workflow runs the same repository gate on pull requests and pushes to main. Unit and integration tests run on Linux, macOS, and Windows. Third-party actions are pinned to full commits.

Local release gate

uv sync --locked
uv run ruff check .
uv run ruff format --check .
uv run ty check
uv run pytest
uv run forge generate --check
uv run forge check
uv run zensical build --clean --strict

Pydantic owns forge-specific catalog, provenance, marketplace, and MCP semantic contracts. Vendored JSON Schema remains authoritative for Agent Plugins plugin.json and mcp.json. Schema bytes are pinned by complete checksums for offline validation.

Client acceptance matrix

Before release, record exact versions and test both the installed user journey and direct contributor workflow:

  1. run Chat: Install Plugin from Source against the exact public repository in an isolated VS Code profile, accept the source trust prompt, select agent-plugin-forge when a multi-entry marketplace presents a picker, confirm that it shows Manage, and find package-agent-skill in Chat: Configure Skills...;
  2. run the packaged bootstrap helper against an isolated Git remote and verify temporary creation, alternate origin, persistent reuse, clean main, and exact revision;
  3. install the same package in isolated Copilot CLI and Codex homes;
  4. open a disposable contributor clone in VS Code and run the manual tutorial commands;
  5. install a local portable fixture with Chat: Install Plugin from Source, confirm its skill and MCP server, and call a credential-free tool.

Marketplace command pairs:

copilot plugin marketplace add MiguelElGallo/agent-plugin-forge
copilot plugin install agent-plugin-forge@agent-plugin-forge
copilot plugin list

codex plugin marketplace add MiguelElGallo/agent-plugin-forge
codex plugin add agent-plugin-forge@agent-plugin-forge
codex plugin list

Use isolated client homes for repeatable tests. Do not remove or replace a user's existing marketplace registrations during acceptance.

For VS Code update acceptance, run Extensions: Check for Extension Updates and confirm the new plugin version before relying on the approximately daily automatic check.

Treat local-origin and private-host acceptance as separate checks. A disposable local Git source qualifies offline review, origin hashing, and refusal to publish without a GitHub endpoint.

Private-marketplace qualification requires a disposable private GitHub.com or GitHub Enterprise Server remote. Confirm each client accepts its documented HTTPS or SSH form, every form resolves to the intended repository, the review prompt retains the private origin, and publication derives its authentication host and pull-request target from that origin. Never place real private credentials in fixtures or logs.

Publish and read back

Merge only the reviewed head SHA after every required check succeeds. Then verify clean main, the live GitHub ruleset, generated marketplace bytes, a fresh marketplace install, and the deployed Zensical site. Documentation deploys only from main.