Releases: MuhammadBahaa/majarrah-marketplace
Releases · MuhammadBahaa/majarrah-marketplace
Release list
skill-craft 1.1.0
1.1.0 - 2026-07-28
Review output contract update — the first release that changes what a review
prints:
- Score every review out of ten on the Verdict line. The verdict picks the
band (BLOCKED 0–3, NEEDS-WORK 4–6, READY-WITH-FIXES 7–8, READY 9–10) and the
count of findings at the worst severity picks the place inside it, so two
runs of one review land on the same number. - Hold the score to the verdict's as-submitted discipline: applying a fix
never raises it, and a number outside its band is an error, not a judgment
call. - Turn the Findings table into a restricted template — five fixed columns and
a placeholder row — and enforce it in the skill's own red flags instead of
describing it in prose. - Make each finding's Location a clickable
file:linelink relative to the
working directory, so an approver opens the file on the defect's line
instead of hunting for it.
skill-craft 1.0.7
1.0.7 - 2026-07-23
Repository-metadata release (supersedes the unpublished 1.0.6, whose release
workflow failed validation before it could run):
- Show live release, license, and star badges on both public READMEs, so the
published version and repo signals read straight from GitHub. - Move the distribution repo's GitHub "About" data (description, homepage,
topics) and its marketplace identity into source-controlled
distribution/<target>.meta.json, replacing values hardcoded insync.py. - Check that data against the live repo on every release, and apply it
automatically when an admin-scoped token is configured. - Fix the release workflow:
secretsis not a valid context in a step-level
if:, so the token presence check moved inside the step. - No skill behavior, review rules, or output contracts changed.
skill-craft 1.0.5
1.0.5 - 2026-07-23
Documentation and release-infrastructure update:
- Rebalance both public README install sections so Codex, Claude Code,
skills.sh agents, and manual copy each get equal, parallel instructions. - Publish a GitHub Release for every synced plugin version, so the
distribution repo's Releases sidebar tracks what is actually published. - Sync the whole
distribution/<target>/tree, not just the README, so the
distribution repo's own workflows stay generated from source. - No skill behavior, review rules, or output contracts changed.