Skip to content

ProdPilot v1.0.0

Choose a tag to compare

@github-actions github-actions released this 20 Sep 14:46
· 35 commits to main since this release

The first stable release. What changed is what the project now promises, how
widely it is tested, and two faults that running the suite on Windows for the
first time uncovered.

Fixed

  • A Docker daemon in Windows container mode was reported as available, and
    every build then failed with "no matching manifest for windows/amd64" and no
    classification. ProdPilot now says the daemon runs Windows containers and
    that its images are Linux, which names what to change.
  • On Windows, the credential file was reported as readable by other accounts
    when the only entries left were SYSTEM, the Administrators group and OWNER
    RIGHTS. The first two read every file on the machine whatever a file's
    entries say, and they survive breaking inheritance on an account that is an
    administrator, so the warning could not be acted on; they are now expected
    and named in the report. OWNER RIGHTS is not an account at all, but a bound
    on what the file's owner may do, so it is not counted. Any other account on
    the file is still a fault.

Added

  • docs/stability.md: what 1.x keeps stable. The five tool
    names and their fields, the rule identifiers, the commands and their flags,
    where credentials live, and the gate's three conditions. It also says what is
    not promised, including the score a given project receives, the number of
    rules and the model's estimates.
  • The test workflow runs on Windows as well as Linux and macOS, so the platform
    ProdPilot is developed on is covered by its own suite.
  • The packaged wheel is installed outside the repository on all three systems,
    and the shipped model is loaded there, so what pip install prodpilot gives
    a user is checked on each of them.
  • Files published to PyPI carry attestations, so anyone can check that they
    were built by this repository's release workflow.

Known limits

These are unchanged from the release candidates and are stated here rather than
dropped:

  • Supported stacks are Node.js with Express and React with Vite; the only
    deployment target is Render.
  • How often a live agent's delegated fix passes verification has not been
    measured across the six delegated rules.
  • Not yet observed end to end on a real service: the deploy tool called by an
    IDE agent, and the CI/CD workflow ProdPilot writes redeploying a live service
    from GitHub Actions. The nine stages and the generated workflow are covered
    by the suite against scripted APIs.
  • Render's own automatic deploy stays on, so a push can start a second deploy
    beside the workflow's; the workflow waits for the newer one.