Vladimír Gorej

Linking another auto-merge GitHub Action which suffers from this issue https://github.com/ridedott/merge-me-action/issues/814

Just for people looking for solution to this: At the end, this article contains new updated section (search for: **Update: 16.3.2021**) with possible solution to the problem. https://www.linkedin.com/pulse/how-keep-your-npm-dependencies-up-to-date-without-wasting-gorej/

@BetaHuhn is the checkout necessary in your example? When you leave it out the behavior of the workflow is equivalent with the workflow without it.

@BetaHuhn I've run tests and got the exact same results with or without it. Some examples in README contains checkout, some don't. Maybe it would warrant some explanation, so that...

Can we pls push this PR ? We're not able to use this library without full license text. MIT requires that. Please...

Would be great to have it included in default plugins for gh-pages

Do I correctly assume that `2.4.1` release effort was discontinued? Given we already have [2.5.0](https://github.com/asyncapi/spec/issues/830) effort on the way.

https://github.com/asyncapi/spec/pull/783 has been merged directly to master. Closing.

> Do we really have to do `2.4.1`? In my opinion No, it's not really necessary, I've just suggested it given the quick cadence of release process for the spec....

> The spec is defined in this repository, and not in the json schema definitions (those are supporting the spec, not defining them IMHO) This has come up multiple times...