Should All PRs include a changeset?

[KhudaDad414]

Reason/Context

Currently, a PR doesn't need to include any changeset. It means that we can have PR that doesn't trigger a release in any package. it allows maintainers and contributors to include a changeset and select which package they want to bump, and whether it is a breaking change or not.

IMO If something changes in the studio app, it makes sense to release. But there are other packages and the design system. Sometimes change is only made to the docs.

We ignored the release in semantic release by prefixing it with docs, or chore. With changesets, we just don't include any changesets.

Curious to know if there are any alternatives and what problem it cause.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️