When removing a message from AsyncAPI the catalog needs to reflect this.

I believe at the moment if you delete a message on AsyncAPI, and you already have generated your Catalog, the message will not be removed. It would be nice to handle this for users.

Only way I can think this to work, is to check the previous version if its there, and do a diff, if something is gone then we need to remove it in the catalog....., not sure if this is desired behaviour or not..... will continue to look into this.