[FEATURE] implementation of a predeploy environment for the CLI releases.

[neoandmatrix]

Why do we need this improvement?

Currently the new versions of CLI are directly released into the public for use. But sometimes these might have a bug or error due to some other package which can break other users workflow who are using the CLI.

How will this change help?

This change will allow to enhance the testing of CLI releases before releasing them for the public use.

Screenshots

No response

How could it be implemented/designed?

Needs to be discussed further.

🚧 Breaking changes

No

👀 Have you checked for similar open issues?

• [x] I checked and didn't find a similar issue

🏢 Have you read the Contributing Guidelines?

• [x] I have read the Contributing Guidelines

Are you willing to work on this issue?

None

[Souvikns]

Cli does not auto update, it is up to the user to update. So if the user chooses to update and if anything breaks then the user can always roll back.

[neoandmatrix]

Cli does not auto update, it is up to the user to update. So if the user chooses to update and if anything breaks then the user can always roll back.

Many users use it directly from npx and if a release has bugs it might affect them.

[Souvikns]

We follow a release workflow from https://github.com/asyncapi/.github/ maybe you can open this issue there. The workflows are synced from that repo. So for making any changes to the workflow changes need to be made there.

[neoandmatrix]

We follow a release workflow from https://github.com/asyncapi/.github/ maybe you can open this issue there. The workflows are synced from that repo. So for making any changes to the workflow changes need to be made there.

Thanks for the direction, but now as this is taken up by @AayushSaini101 the implementation is upto him now.

Thanks.

[AayushSaini101]

@Shurtu-gal do we still need this ?

[github-actions[bot]]

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

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 :heart: