apigee / apigee/apigeetool-node
Changelog missing
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 91
- Forks
- 91
- PR merge metrics
- No merged PRs in 30d
Description
Hi
I see a new release version v0.15.0 but I cant find what has changed and why should I update or not. I was also confused seeing the release section at the repository main page showing "Release v0.9.0" as latest. Indeed while checking the commits I saw the tags on the release commits but as github does not care that much about git tags it was not super prominent and I still would need to check commits for the changes made.
Ideas
- Have a CHANGELOG.md file maybe with this format https://keepachangelog.com/en/1.0.0/ to keep record that
- Start again usage of github releases to document it
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.
Research direction
Start by inspecting the repository's existing release tags and GitHub release history, especially v0.15.0 and the displayed v0.9.0 release. Define where release changes should be recorded and how the latest release should be presented; done means users can find the changes and upgrade context for current releases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- documentation, release
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100