feat: re add protobuff parser

[GreenRover]

re enable protobuff parser lib

[fmvilas]

LGTM 👍

[GreenRover]

/rtm

[smoya]

/rtm

[smoya]

Would it make sense to merge this into master directly? Supporting protobuf here doesn't need to wait anything else isn't?

[GreenRover]

It can go in the master as well. But this pr is not compatible with master.
Is there a release timeline for next major?

[smoya]

I see the next branch is using the ^3.0.0-next-major-spec.1" version of the parser. If instead we use the latest release (not prerelease) then would be able to merge to master I guess. Is there any strong reason this to be blocked by the release of v3 of the spec? Pinging @jonaslagoni who worked on the new parser adoption in this repo.

[jonaslagoni]

Lets just do the change to next, its the only place where it makes sense.

And it already is there on master, so no need to change anything there. Its only relevant on next because I had to disable it after the rewrite to parser v3.

[GreenRover]

@jonaslagoni protobuf-parser was not jet part in master. I only add it for next branch so far. Here the pr for master #759

[jonaslagoni]

Ahh, right @GreenRover 👍

[GreenRover]

Back to this issue. What needs to be done to get it merged?

[jonaslagoni]

I really dont see it as necessary to add it to master as well, but of course if you use v0 somewhere it would be nice to have 😄

[GreenRover]

Me neither, i would prefer to get next released because it fixes many of my open issue with current release.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[asyncapi-bot]

🎉 This PR is included in version 1.0.0-next.53 🎉

The release is available on:

• npm package (@next dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[GreenRover]

Any one an idea why only react-component:
https://www.npmjs.com/package/@asyncapi/react-component/v/1.0.0-next.53?activeTab=versions
gots an new release.
But the web-component not:
https://www.npmjs.com/package/@asyncapi/web-component?activeTab=versions

[derberg]

@GreenRover I think it is cause all by outdated pipelines -> https://github.com/asyncapi/asyncapi-react/actions/runs/6111938173/job/16588288332

let's just release -> #761