Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: merge master into next major spec #787

Merged

Conversation

fmvilas
Copy link
Member

@fmvilas fmvilas commented Jun 13, 2023

I'm merging the master branch into next-major-spec and fixing all the conflicts 😅

smoya and others added 30 commits April 27, 2022 16:43
Co-authored-by: asyncapi-bot <info@asyncapi.io>
Co-authored-by: asyncapi-bot <info@asyncapi.io>
@fmvilas
Copy link
Member Author

fmvilas commented Jun 13, 2023

Can someone guess why npm test is failing? It complains that cross-env is not installed but it's on the package.json file. And it's running well on my machine 🤔

@smoya
Copy link
Member

smoya commented Jun 13, 2023

Can someone guess why npm test is failing? It complains that cross-env is not installed but it's on the package.json file. And it's running well on my machine 🤔

For some reason, we are not catching errors on npm install step. There are some in this case https://github.com/asyncapi/parser-js/actions/runs/5257292254/jobs/9500449903#step:8:2227

@fmvilas
Copy link
Member Author

fmvilas commented Jun 13, 2023

Good catch! I found it on my system by deleting node_modules. It's a corrupt package-lock.json file. I'm pushing a new one.

@sonarcloud
Copy link

sonarcloud bot commented Jun 13, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 11 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

Copy link
Member

@jonaslagoni jonaslagoni left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why does all these v3 model changes show up? 🤨 Master does not contain any v3 changes?

@fmvilas
Copy link
Member Author

fmvilas commented Jun 13, 2023

master doesn't but next-major-spec does. This PR is not only merging master but also fixing the problems that appeared after doing that. What you see is that, the changes that I had to do to make it work after merging.

@jonaslagoni
Copy link
Member

master doesn't but next-major-spec does. This PR is not only merging master but also fixing the problems that appeared after doing that. What you see is that, the changes that I had to do to make it work after merging.

Ahhh, gotcha 👍

Copy link
Member

@jonaslagoni jonaslagoni left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jonaslagoni
Copy link
Member

REMEMBER TO MERGE COMMIT

@jonaslagoni
Copy link
Member

/dnm

@fmvilas fmvilas merged commit f551deb into asyncapi:next-major-spec Jun 13, 2023
@fmvilas fmvilas deleted the merge-master-into-next-major-spec branch June 13, 2023 16:33
@asyncapi-bot
Copy link
Contributor

🎉 This PR is included in version 2.0.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

@jonaslagoni
Copy link
Member

🎉 This PR is included in version 2.0.3 🎉

The release is available on:

* [npm package (@latest dist-tag)](https://www.npmjs.com/package/@asyncapi/parser/v/2.0.3)

* [GitHub release](https://github.com/asyncapi/parser-js/releases/tag/v2.0.3)

Your semantic-release bot 📦🚀

Huh?

@fmvilas
Copy link
Member Author

fmvilas commented Jun 14, 2023

Weird 🤔 @KhudaDad414 you're the most familiar with GitHub actions along with Lukasz. Any idea what's happening?

@KhudaDad414
Copy link
Member

I am assuming it's because of this comment. #717 (comment) 🤔
commit are not included in the release(no possible 😆 ) so I guess we can ignore.

@fmvilas
Copy link
Member Author

fmvilas commented Jun 15, 2023

Are you saying that a comment triggered the release? o.O

@KhudaDad414
Copy link
Member

The release isn't triggered for this branch. It's just a mistrigrered comment.

@asyncapi-bot
Copy link
Contributor

🎉 This PR is included in version 2.1.0-next-major-spec.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

@asyncapi-bot
Copy link
Contributor

🎉 This PR is included in version 2.2.0-next-major-spec.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.