Skip to content
This repository was archived by the owner on Oct 13, 2026. It is now read-only.

Make release proof independent of installed agent plugins - #70

Merged
lukemaj merged 1 commit into
mainfrom
fix/68-isolated-release-proof
Sep 23, 2026
Merged

lukemaj merged 1 commit into
mainfrom
fix/68-isolated-release-proof

Conversation

@lukemaj

@lukemaj lukemaj commented Sep 23, 2026 •

Copy link
Copy Markdown
Contributor

The first automatic release failed because existing deterministic tests relied on the developer's installed skills, plugins and MCP inventory. A clean GitHub runner has none, so fake harnesses were blocked before execution.

Run the complete suite through an entry point that reuses disposable fake homes. Production validation remains enabled, user configuration stays untouched, and fixtures are removed afterward. Share one read-only proof workflow between pull requests and release runs. The separate publishing job has write permission and requires successful proof.

Closes #68. Repairs #69. Version: 0.25.0 → 0.25.1.

Validation at f5f67d9f3eece67b21194317735f82c7f01e87f2: the complete 515-test suite passes on macOS (one opt-in discovery skip) and GitHub Ubuntu/Python 3.13 (that skip plus the case-insensitive-filesystem test). The CI merge tree matches the reviewed candidate exactly. Independent Astra/high review has no findings. Compileall, versionctl CI doctor, exact-commit release validation and diff checks pass. Canonical proof and handoff.

Workflow lint passes with the existing narrow suppression for concurrency.queue, whose syntax is checked against GitHub's current concurrency contract. This follow-up has not been merged or released. Marketplace promotion still requires its missing 1.5.0 base release.

@lukemaj
lukemaj marked this pull request as ready for review September 23, 2026 14:29
@lukemaj
lukemaj merged commit ce93662 into main Sep 23, 2026
1 check passed
@lukemaj
lukemaj deleted the fix/68-isolated-release-proof branch September 23, 2026 15:34
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Release versioned merges automatically

1 participant