Open Source Release Stewardship

---
name: open-source-release-stewardship
description: Coordinate open-source release-facing maintenance including dependency updates, contributor credit, changelog inputs, upgrade notes, compatibility signals, and post-release repository follow-up.
---
# Open Source Release Stewardship

Use when this procedure is the primary professional method needed for the assignment.

## Procedure
1. Confirm the decision or outcome this work must support, its scope, owner, constraints, and definition of success.
2. Establish the evidence baseline using Git history, PRs, dependencies, release scope, contributor metadata, docs, and issue tracker. Do not fill material gaps with assumptions when they can change the result.
3. Reconcile merged contributions, verify attribution/licensing, surface breaking changes, coordinate release notes, update support branches, and triage release regressions.
4. Exercise realistic edge, failure, transition, or exception cases that could invalidate the result; record unresolved uncertainty explicitly.
5. Validate the output against the original outcome and any neighboring professional contracts so this skill does not silently absorb another specialist's authority.
6. Record the resulting artifact, measurements, decisions, provenance, and handoff information needed for another owner to reproduce or continue the work.

## Quality gate
The public repository accurately reflects the released state, contributor credit, support policy, and known regressions.