What would you like
The release artifact forge-workflow.zip should contain the repository's LICENSE file.
The problem it solves
The plugin is MIT licensed, declared in .claude-plugin/plugin.json and in a LICENSE file at the repository root. But the manual-install artifact has never carried it. Checked against every release so far:
- v0.1.0: no LICENSE in the zip
- v1.0.0: no LICENSE in the zip (21 entries)
- v1.1.0: no LICENSE in the zip (22 entries)
Someone who installs by downloading the zip and extracting it into ~/.claude/skills/ therefore ends up with the code and no license text anywhere near it. Anyone who installs through the marketplace gets the git contents and is fine, so this only affects the manual path.
It is worth fixing on Forge's own terms. forge-standards tells the projects Forge builds that "a repository with no LICENSE file is all rights reserved by default, not permissive", and this repo is supposed to hold itself to the standards it enforces on others. Shipping MIT code in a bundle with no license is exactly the ambiguity that rule exists to prevent.
What to change
Add LICENSE to the set of files copied into the zip when cutting a release. The current payload is:
forge-workflow/README.md
forge-workflow/.claude-plugin/plugin.json
forge-workflow/hooks/hooks.json
forge-workflow/scripts/*.js
forge-workflow/skills/*/SKILL.md
forge-workflow/templates/*
so this is one more line, plus a note in CLAUDE.md under "Publishing changes to users" so the next person building an artifact by hand does not drop it again. Worth considering whether the packaging step should be a small script rather than a manual copy, since a hand-assembled artifact is how the omission survived three releases.
Anything else
Not urgent and not a defect in the shipped behaviour, so it does not warrant a release of its own. Fold it into whatever version ships next.
Noticed while building the v1.1.0 artifact and matching its layout against v1.0.0.
What would you like
The release artifact
forge-workflow.zipshould contain the repository'sLICENSEfile.The problem it solves
The plugin is MIT licensed, declared in
.claude-plugin/plugin.jsonand in aLICENSEfile at the repository root. But the manual-install artifact has never carried it. Checked against every release so far:Someone who installs by downloading the zip and extracting it into
~/.claude/skills/therefore ends up with the code and no license text anywhere near it. Anyone who installs through the marketplace gets the git contents and is fine, so this only affects the manual path.It is worth fixing on Forge's own terms.
forge-standardstells the projects Forge builds that "a repository with no LICENSE file is all rights reserved by default, not permissive", and this repo is supposed to hold itself to the standards it enforces on others. Shipping MIT code in a bundle with no license is exactly the ambiguity that rule exists to prevent.What to change
Add
LICENSEto the set of files copied into the zip when cutting a release. The current payload is:so this is one more line, plus a note in
CLAUDE.mdunder "Publishing changes to users" so the next person building an artifact by hand does not drop it again. Worth considering whether the packaging step should be a small script rather than a manual copy, since a hand-assembled artifact is how the omission survived three releases.Anything else
Not urgent and not a defect in the shipped behaviour, so it does not warrant a release of its own. Fold it into whatever version ships next.
Noticed while building the v1.1.0 artifact and matching its layout against v1.0.0.