-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[META] Introduce keep-a-changelog to all clients #33
Comments
How has this been going for core? If it's hunky dory, it makes sense to raise the bar for client repos. |
Here's another example why we should do this: opensearch-project/opensearch-js#290 (comment) - user is reading docs that are newer than the released software and I can't tell what was released in the last version vs. what was added since |
This is complete across all clients and can be closed. I'm tracking the discussion in opensearch-project/OpenSearch#4936 and will update the implementation if anything changes. |
I noticed we don't do CHANGELOG updates in some dependabot PRs, can we please fix that? |
It's weird. We have the dependabot_pr action that should update the changelog if the PR is raised by dependabot. But sometimes we have to manually do a dependabot recreate to get it to update the changelog. |
What kind of business use case are you trying to solve? What are your requirements?
Release notes are of varying quality. Similar to opensearch-project/OpenSearch#1868.
What is the problem? What is preventing you from meeting the requirements?
What are you proposing? What do you suggest we do to solve the problem or improve the existing situation?
An implementation of this was done in OpenSearch core in opensearch-project/OpenSearch#4085. Copy-paste that into all clients.
The text was updated successfully, but these errors were encountered: