Improve automation w.r.t. changeset addition

[Shurtu-gal]

Currently the changeset procedure throws a wrench into the current CI/CD pipeline as addition of it is manual.

This leads to the following problems:

• Automated PRs by bot are merged without changeset leading to no release happening.
• Sometimes maintainers overlook absence of changesets, leading to critical bug fixes not getting released.

Current POA:
Step 1. Add changeset based on title of pull request.

• feat --> minor
• fix --> patch
• feat! or fix! --> major

Step 2. Messages for releases need to be thought of a little more.
Step 3. Some way to remind contributors to modify changeset.

Note: Just an initial idea in my mind.

Are you willing to work on this issue ?
Yes (at least for now)

[Shurtu-gal]

bounty/candidate

[imabp]

@Shurtu-gal I would like to work on this.

[Shurtu-gal]

Hello @imabp 👋, great to have you back. Actually I was planning on picking this up 😅.

[imabp]

Haha, @Shurtu-gal in that case, do we have something else where I can pick up from?
I was just trying to get my hands dirty on things again ❤

[Shurtu-gal]

Sure, there will be multiple ones. Some good candidates might be studio ones like docs generation or installation of google analytics.

You can always scour and find some high priority, difficult issue though.

[aeworxet]

Bounty Issue's service comment

Text labels: bounty/2025-Q2, bounty/advanced, bounty/coding
First assignment to regular contributors: 2025-03-21 00:00:00 UTC+12:00
End Of Life after: 2025-04-30 23:59:59 UTC-12:00

@asyncapi/bounty_team

The Bounty Program is not a Mentorship Program. The accepted level of Bounty Program Participants is Middle/Senior.

Regular contributors should explain in meaningful words how they are going to approach the resolution process when expressing a desire to work on this Bounty Issue.

[Shurtu-gal]

I wish to take up this bounty issue.