Skip to content

Agent Plugin Forge 1.0.0

Choose a tag to compare

@MiguelElGallo MiguelElGallo released this 12 Sep 06:51
dc48477

Agent Plugin Forge 1.0.0 makes the publication destination an explicit user choice. Asking the installed Forge to publish a skill no longer selects the project's public repository automatically.

  • First use asks where to publish, confirms the exact URL, and can remember one default across projects.
  • Later requests reuse that saved destination and show it in every review plan.
  • One-time overrides preserve the saved default. Replacing a different default requires explicit confirmation.
  • The bootstrap helper stops before cloning when no destination is configured. Invalid settings also stop the operation, and concurrent saves cannot overwrite another client's choice without explicit replacement. Settings replacements are written atomically.
  • The shipped skill, setup and publication guides, private-marketplace guidance, CLI reference, troubleshooting, and release documentation describe the same workflow.

Each publication still follows plan, review, approval, and implementation. A saved destination does not authorize an import, push, pull request, or merge.

Upgrading

Refresh the Forge marketplace, update the installed plugin, verify version 1.0.0, and start a new chat. Your first publication will ask for a destination unless one is already explicitly configured. Automated bootstrap callers must supply --origin, set AGENT_PLUGIN_FORGE_ORIGIN, or save a confirmed default; there is no built-in repository fallback.

Upgrade instructions · Publication workflow · Saved destination settings

Validation

The local suite passed 288 tests on Python 3.11.16 and 3.12.13, with two platform-specific skips per run and 92% coverage. Ruff, formatting, ty, Forge validation, generation drift checks, skill validation, actionlint, and the strict documentation build passed. The real CLI tutorial covers a remembered destination through review, approved apply, generation, and validation.

The wheel installed into a fresh environment and passed version, branch-name, and repository validation commands. A local Copilot CLI 1.0.84-1 configuration loaded the 1.0.0 plugin and its skill. The benchmark workflow smoke test used isolated destination settings.

After the protected merge, a fresh public marketplace installation in Copilot CLI 1.0.84-1 installed version 1.0.0 with one skill. All nine installed package files and executable modes matched the merged source. The installed helper refused an unset destination, reused a remembered destination from another project, preserved the default during a one-time override, and refused an unconfirmed replacement. These are client installation and deterministic helper checks; they do not claim a full agent publication invocation. The deployed upgrade, publication, compatibility, and CLI documentation was read back successfully.

Published from PR #13 after quality and the Linux, macOS, Windows, and Python 3.11 CI checks passed. Exact client and historical qualification boundaries are in the compatibility evidence.

Artifacts

The wheel and source distribution provide the Python Forge CLI. Install the Forge plugin through the Git marketplace using the client installation instructions. Verify downloaded archives against the attached SHA256SUMS.