[CI] Follow standard release process and conventions
Open
@nebula-aac is already working on this.
Since Nov 12, 2023.
area/ci
- Dominant language
- TypeScript
- Stars
- 137
- Forks
- 239
- Avg merge
- 4d 14h
- Merged PRs (30d)
- 5
Description
Current Behavior
- Releases are currently not following the naming scheme used in all other projects.
- Releases are currently not using release notes generated by the release-drafter workflow.
- Releases are currently being packaged and published via manual GitHub workflow invocation or another process?
Desired Behavior
- Please use "Project Name v<semver>" as the release name.
- Please use release notes that are auto-generated by the https://github.com/layer5io/sistent/blob/master/.github/release-drafter.yml (runs).
- Please confirm that release packages are built and published to npm.org editing and publishing from the Releases page.
Contributor Guides and Resources
- 🛠 Meshery Build & Release Strategy
- 🎨 Wireframes and designs for Layer5 site in Figma (open invite)
- 🙋🏾🙋🏼 Questions: Layer5 Discussion Forum and Layer5 Community Slack
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.