Proposal: Move diff, bundler, and optimizer into CLI

[princerajpoot20]

As part of the 2026 community goals (more details here: asyncapi/community#3495), we conducted an audit of all repositories. The summary of the findings can be found here: asyncapi/community#3495 (comment).

As suggested by @deberg, we are proposing to move the diff, bundler, and optimizer repositories to the CLI repository.

Reference to the conversation:

• https://asyncapi.slack.com/archives/C34F2JV0U/p1774973085382029?thread_ts=1774874525.585229&cid=C34F2JV0U
• [2026 Goals][S1] Repository Audit & Consolidation (Targets O1, O2) community#3495

I am opening this issue to gather feedback and approval from the code owners of this repository regarding the proposal to move diff, bundler, and optimizer repository to CLI.

Tagging all code owners for their feedback and approval.
@Souvikns @Amzani @Shurtu-gal @AayushSaini101

[AayushSaini101]

Approved : )

[Shurtu-gal]

Approved. But need a little bit of clean up before we move forward with this.
@neoandmatrix is already working on the clean up part.

[princerajpoot20]

@Shurtu-gal sure, Sure, sounds good. Is there an issue where we can track this cleanup work, or could you provide a rough timeline for the cleanup if you have one in mind?

[neoandmatrix]

Hi, @princerajpoot20 I have opened an issue here
#2252 . Almost done with first. Will be updating soon.

Thanks.

[Amzani]

Love the idea but as @Shurtu-gal said - we need to make CLI first ready to welcome new code.

[AayushSaini101]

Reason for the Advanced Classification

The Advanced Classification is required because of the following list of work that needs to be completed in order to resolve this issue:

• Consolidating three repos (diff, bundler, optimizer) into asyncapi/cli requires turning CLI into a Turborepo monorepo with npm workspaces — it is not one today.
• Each package must be migrated, rewired to workspace dependencies, and keep the same npm name and public API with no breaking changes.
• A new multi-package release pipeline (Changesets + npm Trusted Publishing) is needed so all four packages publish independently from one repo.
• The work also covers CODEOWNERS merge, CLI prerequisite cleanup (#2252), specs/docs updates, and end-to-end validation across repos.

[princerajpoot20]

@AayushSaini101 i am taking care of all this merger