Some checks failed
Flatpak / flatpak (push) Has been cancelled
A push to master published the build as the rolling `beta` branch and refreshed a `latest` prerelease; a tag cut the stable release. Now every push to master is the release: CI takes the version from the metainfo's newest <release>, publishes `stable`, tags the pushed commit and creates the release with that entry's notes. A version that is released already fails the job before anything is built or published, and so does a lookup that cannot tell, so a push to master adds a new <release>. Publishing is master's alone: a manual run on another branch builds and tests and cuts nothing. Tags are no longer a trigger, and the rolling `beta` and `latest` steps are gone. The README and AGENTS say so, and the first release's entry, 1.0.0, takes the date of its push and names what it ships.
45 lines
2.6 KiB
XML
45 lines
2.6 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!-- SPDX-License-Identifier: CC0-1.0 -->
|
|
<component type="console-application">
|
|
<id>net.catcrafts.CrafterReview</id>
|
|
<name>Crafter Review</name>
|
|
<summary>Adversarial pre-push review of a frozen commit range</summary>
|
|
<metadata_license>CC0-1.0</metadata_license>
|
|
<project_license>AGPL-3.0-only</project_license>
|
|
<developer id="net.catcrafts">
|
|
<name>Catcrafts</name>
|
|
</developer>
|
|
<description>
|
|
<p>
|
|
The pre-push review pipeline: crafter-review freezes a commit range,
|
|
partitions it into units, and runs adversarial lenses over it — the
|
|
approach, the running application through the Playwright MCP server,
|
|
a bug proof and a security review — one claude process per unit, on the
|
|
seats the repository or the machine provides. A range is send-ready
|
|
only when every gate passes on the exact frozen hash.
|
|
</p>
|
|
</description>
|
|
<url type="homepage">https://forgejo.catcrafts.net/Catcrafts/Crafter.Review</url>
|
|
<url type="bugtracker">https://forgejo.catcrafts.net/Catcrafts/Crafter.Review/issues</url>
|
|
<url type="vcs-browser">https://forgejo.catcrafts.net/Catcrafts/Crafter.Review</url>
|
|
<provides>
|
|
<binary>crafter-review</binary>
|
|
</provides>
|
|
<content_rating type="oars-1.1"/>
|
|
<releases>
|
|
<release version="1.0.0" date="2026-11-02">
|
|
<description>
|
|
<p>New</p>
|
|
<ul>
|
|
<li>Pre-push review gates for a commit range: Claude processes review the approach, the running application, a bug proof, security and the commit messages, and a range is send-ready only when every gate passes on its exact frozen hash.</li>
|
|
<li><code>crafter-review init</code> sets a repository up: its config and the <code>/prepush</code> skill.</li>
|
|
<li>Modes in the repository's config (<code>modes.<name></code>): the kind of artifact, the lenses it runs and their effort. Every lens is off until a mode lists it.</li>
|
|
<li>Seats from a dotenv file - <code>--env-file</code>, <code>$SEATS_ENV_FILE</code>, the working directory's <code>.env</code> or the machine's own <code>~/.config/crafter-review/env</code> - over the environment's, on one seat board for every driver on a machine.</li>
|
|
<li>A repository's own section appended to a lens's charter (<code>lenses.<name>.section</code>).</li>
|
|
<li>Pre-send review of a kernel patch series or a mailing-list reply (<code>--mode series</code>, <code>--mode reply</code>).</li>
|
|
<li>Shipped as a Flatpak with its own git, Node and ripgrep.</li>
|
|
</ul>
|
|
</description>
|
|
</release>
|
|
</releases>
|
|
</component>
|