Publish changelog of the sdks
Open
Nobody has claimed this yet.
feat
- Dominant language
- Shell
- Stars
- 96
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
Preflight checklist
- I could not find a solution in the existing issues, docs, nor discussions.
- I agree to follow this project's Code of Conduct.
- I have read and am following this repository's Contribution Guidelines.
- This issue affects my Ory Network project.
- I have joined the Ory Community Slack.
- I am signed up to the Ory Security Patch Newsletter.
Describe your problem
Would be great to see a changelog somewhere as to what is fixed or what changes between versions? There's this repository, but the commits are also not that helpful. Any chance this could be added?
Describe your ideal solution
See a changelog of what changes between versions to know what to look out for. Or which bugs are fixed.
Workarounds or alternatives
Blind upgrades
Version
n/a
Additional Context
No response
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 with the linked SDK repository commit history, which the issue identifies as insufficient. Define where the changelog belongs and how it should describe changes and fixed bugs between versions; done means users can review those differences before upgrading.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, release
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100