Define a release and versioning workflow #19
Description
User Story
As a maintainer, I want a release and versioning workflow so that the project can publish stable milestones and communicate changes clearly.
Context
Even an open source fellowship project benefits from good release hygiene. This issue should establish a lightweight release process that can grow with the repo.
Acceptance Criteria
- The repo has a documented release/versioning strategy
- Release notes can be generated or curated in a repeatable way
- The workflow supports tagging meaningful project milestones
- The release process fits the chosen package and deployment setup
- Contributors understand how user-facing changes should be recorded
Notes
- Keep the first version simple
- Favor transparency and repeatability over elaborate automation
- This issue should help future public contributors understand project movement
Out of Scope
- Full package publishing to npm unless the project needs it immediately
- Enterprise-style release trains
Size
Medium