Work on 2.6.0 release

[AceTheCreator]

Release 2.6.0 is scheduled for January 2023

Detailed info:

• https://github.com/asyncapi/spec/blob/master/RELEASE_PROCESS.md

Kick-off:

* link to recording of community call where the new release was started

Release branches:

• https://github.com/asyncapi/spec/tree/next-spec
• https://github.com/asyncapi/spec-json-schemas/tree/next-spec
• https://github.com/asyncapi/parser-js/tree/next-spec

Release notes:

• draft PR - https://github.com/asyncapi/website/pull/PULLREQUEST

Progress:

• Create release branches
  • spec - https://github.com/asyncapi/spec/tree/next-spec
  • spec-json-schemas - https://github.com/asyncapi/spec-json-schemas/tree/next-spec
  • parser-js - https://github.com/asyncapi/parser-js/tree/next-spec
• Update release branches from forks
  • spec - chore: update next-spec with latest master #892
  • spec-json-schemas - chore: update next-spec with latest master spec-json-schemas#301
  • parser-js - chore: update next-spec with latest master parser-js#691
• Update release branches with new versions
  • spec chore: update release branch #895
  • spec-json-schemas chore: create definitions for 2.6.0 version of the spec spec-json-schemas#302
  • parser-js chore: added mime for new version 2.6.0 parser-js#696
• Create draft release notes
• Update release branches from forks
  • spec chore: update release branch #901
  • spec-json-schemas chore: update release branch spec-json-schemas#306
  • parser-js chore: update release branch parser-js#706
• Notify community about release branches
• Check for potential release contributions
• Draft announcement blog post for new features and changes chore(blog): add release note for 2.6.0 release website#1282
• Write release notes for new features and changes
• Prepare pull requests to merge release branches into master
  • spec feat: release for version 2.6.0 of the spec #902
  • spec-json-schemas feat: release for version 2.6.0 of the spec spec-json-schemas#307
  • parser-js feat: release for version 2.6.0 of the spec parser-js#707
• Notify tsc_members about upcoming release
• Merge release branches into master
  • spec spec feat: release for version 2.6.0 of the spec #902
  • spec-json-schemas feat: release for version 2.6.0 of the spec spec-json-schemas#307
  • parser-js feat: release for version 2.6.0 of the spec parser-js#707
• Write release notes for the releases on Github
• Create releases on Github
  • spec
  • spec-json-schemas
  • parser-js
• Update RELEASE_PROCESS doc with any changes

Draft Release notes

https://www.asyncapi.com/blog/release-notes-2.6.0

Features
---
- Added Pulsar Bindings and Protocol to the Specification (#882) (35693fb](https://github.com/asyncapi/spec/commit/35693fb90e230b48a51df952a743a12408995dd1)) ([binding definition](https://github.com/asyncapi/bindings/tree/master/pulsar)) by @VisualBean  

Full Changelog: https://github.com/asyncapi/spec/compare/v2.5.0...v2.6.0

[github-actions]

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[magicmatatjahu]

PR in converter asyncapi/converter-js#162

[derberg]

For the post release task we need to solve one problem that we had with this release. Now we have a long living next-spec branch that stays there forever. When we release candidates, next-spec is tagged with RC name like for example 2.5.0-next-spec.4. Then when we do a release, tag 2.5.0 is added to master.

So what happened with this release was that for 2.6.0, the release candidate on next-spec was 2.5.0-next-spec.5 instead of 2.6.0-next-spec.1.

[9:27:17 AM] [semantic-release] › ℹ  Found git tag v2.5.0-next-spec.4 associated with version 2.5.0-next-spec.4 on branch next-spec

And the reason was that there is no technical information semantic-release have no idea that the las tag is v2.5.0.

It is not possible to check why in previous releases we did not face this issue as logs on CI are not preserved that long.

---

Now problem is also when we are merging changes from master to release branches. Then semantic-release treats these commits as part of the release, so then adds wrong comments to issues like #674

[derberg]

Opened separate issue for ☝🏼
#899

[AceTheCreator]

@asyncapi/tsc_members There's a new release coming up

[AceTheCreator]

AsyncAPI V2.6.0 is finally out 🚀

I'm pinging code owners of the repositories affected so you can do the necessary updates.

• CLI
• HTML Template
• Converter
• AsyncAPI React
• Studio

@derberg @magicmatatjahu @fmvilas @jonaslagoni @M3lkior @Souvikns @KhudaDad414 @smoya

[fmvilas]

@AceTheCreator I think we can close this issue, right?