Publish changelog of the sdks

till commented 1 year ago

Preflight checklist

[X] I could not find a solution in the existing issues, docs, nor discussions.
[X] I agree to follow this project's Code of Conduct.
[X] I have read and am following this repository's Contribution Guidelines.
[X] This issue affects my Ory Network project.
[X] I have joined the Ory Community Slack.
[X] 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

vinckr commented 1 year ago

Hello @till

You can see all relevant changes in the CHANGELOG for the respective project, for example for Ory Kratos: https://github.com/ory/kratos/blob/master/CHANGELOG.md

We will also publish all things relevant to Ory Network in the changelog here: https://changelog.ory.sh/ and announce it in the Ory Slack, especially if there are breaking changes in the SDK (which are very rare)

till commented 1 year ago

How would I go from the sdk release yesterday to the relevant changes in kratos?

I think that's what I am asking. Or how do I know if there are changes?

github-actions[bot] commented 1 month ago

Hello contributors!

I am marking this issue as stale as it has not received any engagement from the community or maintainers for a year. That does not imply that the issue has no merit! If you feel strongly about this issue

open a PR referencing and resolving the issue;
leave a comment on it and discuss ideas on how you could contribute towards resolving it;
leave a comment and describe in detail why this issue is critical for your use case;
open a new issue with updated details and a plan for resolving the issue.

Throughout its lifetime, Ory has received over 10.000 issues and PRs. To sustain that growth, we need to prioritize and focus on issues that are important to the community. A good indication of importance, and thus priority, is activity on a topic.

Unfortunately, burnout has become a topic of concern amongst open-source projects.

It can lead to severe personal and health issues as well as opening catastrophic attack vectors.

The motivation for this automation is to help prioritize issues in the backlog and not ignore, reject, or belittle anyone.

If this issue was marked as stale erroneously you can exempt it by adding the backlog label, assigning someone, or setting a milestone for it.

Thank you for your understanding and to anyone who participated in the conversation! And as written above, please do participate in the conversation if this topic is important to you!

Thank you 🙏✌️

till commented 1 month ago

Ignoring issues is the new stale? :D

aeneasr commented 1 month ago

More like lack of time to do all the things we would need to do. I still think this is valid, but will probably not picked up within the next year.

ory / network