feat: introduce the turborepo to the parser.js

[ayushnau]

Changes Added.

Turborepo Added.
Converted the parser repo to app, inside the turborepo.
Added the required scripts of the turborepo to the root package.json file.

Related issue(s)

Related to: #963

[ayushnau]

link
@smoya please check added the changeset integration.

[ayushnau]

@smoya I think the changesets changes are ready to merge I have still used the changelog (didnt make it false in the config) cause there is ongoing bug in the changesets which they have not given the solution yet. And this is basically causing changesets still search for the CHANGELOG.md inspite of making it false in the config. here is the link changesets/action#256
Also I was needed to install the @changesets/cli also cause once I run the chagnesets/cli command directly with npx it is installing the cli version and correctly working but then the ci is not able to find the changelog causing the error.

See https://github.com/asyncapi/parser-js/pull/1008/files#r1648443871

Shouldn’t be @changesets/changelog-git ? You don’t need the cli package with such change and maybe that's the reason you needed to install it?

Alternatively, can't we just then get rid of the GH action and do the commands manually maybe?

@smoya added the @changelog/git and its working now . without installing the cli.

[smoya]

I assume you properly tested the release on your own branch and npm account @ayushnau.

LGTM

[ayushnau]

tested and it is deployed to npm registry. Just a thing it creates a pr which i have merged manually. which khudad have told that will get merged automatically with the bot, In my case i did by myself.

[ayushnau]

also just one thing do i need to change this or it is fine

the generate asset line (last line. ) cause in testing it doesnt caused any issue.

[smoya]

also just one thing do i need to change this or it is fine the generate asset line (last line. ) cause in testing it doesnt caused any issue.

At a glance, I don't see why the PR would break anything so if you tested and the README's toc is being properly updated + the built app is right, let's skip it.

[smoya]

/rtm

[smoya]

For some reason, Sonarcloud status is not being reported. I see it is ok in https://sonarcloud.io/summary/new_code?id=asyncapi_parser-js&pullRequest=1008

Trying to push an empty commit so it triggers a new CI build.

[smoya]

Trying to push an empty commit so it triggers a new CI build.

No success. BTW, I fixed the .sonarcloud.properties file for you.

[smoya]

I see it is ok in https://sonarcloud.io/summary/new_code?id=asyncapi_parser-js&pullRequest=1008

No, it's not. That instance ran 18 days ago 😮

Additionally, is pointing to a commit that I can't find within the commits of this branch ad50cc4

[aeworxet]

There was an issue with SonarCloud several weeks ago.
There was a long discussion in Slack
https://asyncapi.slack.com/archives/CQVJXFNQL/p1718711108263639
and at the end of the day an issue was opened in .github
asyncapi/.github#306

It seems not to have a simple immediate solution.

[smoya]

It seems not to have a simple immediate solution.

Yeah, I even tried to reset the config on Sonarcloud with no success.
I disabled the check in master branch now.

[smoya]

/rtm

[smoya]

I disabled the check in master branch now.

Found like it seems a workaround. See #1033 (comment)

[ayushnau]

@smoya creating the pr for the multiparser.

[smoya]

For the record, the release didn't work because the release action wasn't triggered when the automated PR was merged.

The guess is that didn't work because of this https://github.com/asyncapi/parser-js/blob/master/.github/workflows/release-with-changesets.yml#L21-L26, however the PR was created as chore (it is ok).

We would need to remove such checks as in https://github.com/asyncapi/studio/blob/master/.github/workflows/release.yml

[asyncapi-bot]

🎉 This PR is included in version 3.2.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀