| name | gds-release-module |
| description | Use this skill only when the owner explicitly asks to release a module according to its declared pin and publication policy. Classify compatibility, verify the exact commit, publish required tag, package, or GitHub Release, and preserve provenance. Do not use it for module implementation or consumer pin updates alone. |
| disable-model-invocation | true |
Contract
Finalize and publish one module artifact under its declared compatibility and
publication contract.
Use when
- A module change is complete and requires a policy-defined release.
Do not use when
- The pin policy permits an unreleased default-branch commit and no release was
requested.
- Consumer pins are the only requested change.
Inputs
- Module repository ID, exact source commit, version impact, and release policy.
- Publication approval and credentials.
Preconditions
- Verify clean source, required checks, public API impact, and final commit OID.
- Run
gds module release --plan.
- Obtain approval for tag, registry, release, and other external writes.
Workflow
- Recheck commit, version, checks, and publication endpoints.
- Apply the immutable release plan.
- Verify tag/package/release identities and provenance.
- Record consumer eligibility without updating consumers automatically.
Stop conditions
Stop on version mismatch, failing checks, mutable or existing conflicting tag,
registry conflict, stale plan, missing provenance, or insufficient approval.
Verification
Run gds module release --verify <operation-id> --json.
Output
Return source commit, compatibility classification, published artifacts and
digests, release policy evidence, and eligible consumer follow-up.
References
No additional runtime reference is required; use the module's compiled release policy.
