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

feat: release for version 2.5.0 of the spec #841

Closed

Conversation

char0n
Copy link
Collaborator

@char0n char0n commented Sep 22, 2022

Refs #830

@char0n
Copy link
Collaborator Author

char0n commented Sep 22, 2022

/dnm

@char0n
Copy link
Collaborator Author

char0n commented Sep 22, 2022

/au

@smoya
Copy link
Member

smoya commented Sep 22, 2022

@char0n the title should containfeat prefix as we are releasing a minor, otherwise the release won't be triggered.

@char0n
Copy link
Collaborator Author

char0n commented Sep 22, 2022

@smoya yep, you're absolutely right. Thanks!

@char0n char0n changed the title chore: bring 2.5.0 release branch to master feat: bring 2.5.0 release branch to master Sep 22, 2022
@char0n char0n changed the title feat: bring 2.5.0 release branch to master feat: release for version 2.5.0 of the spec Sep 28, 2022
@sonarqubecloud
Copy link

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 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@char0n
Copy link
Collaborator Author

char0n commented Sep 28, 2022

This PR has been updated with latest commit from next-spec branch.

@char0n
Copy link
Collaborator Author

char0n commented Sep 28, 2022

@fmvilas @derberg @dalelane can I ask one of you (code owners) to merge this PR which should create a new 2.5.0 release of the specification?

Here are the release notes for the 2.5.0 version of the spec that should be used for the GitHub Release.

Release notes article -> https://www.asyncapi.com/blog/release-notes-2.5.0

Features
---
- Server Variables can be now referenced from inside the Server Object (#776) ([5deef1e](https://github.com/asyncapi/spec/commit/5deef1e9148947689d53db3a1d013d49cd9df7d0)), closes #775 by @char0n 
- Decorating Server Object with tags (#809) ([b0c2f9c](https://github.com/asyncapi/spec/commit/b0c2f9c086d940e8016ec1fa60107fe74cc070db)), closes #654 by @smoya
- Added new Google Cloud Pub/Sub Bindings (#836) ([babc3be](https://github.com/asyncapi/spec/commit/babc3bedb5d85375a305c7268e96257113c1933e)) ([binding definition](https://github.com/asyncapi/bindings/tree/master/googlepubsub)) by @whitlockjc 
- Other enhancements
  - Clarified ChannelItem.$ref resolution rules (#779) ([9a293c7](https://github.com/asyncapi/spec/commit/9a293c77f6bf74a056a8845dabfbe20e73a6f320)), closes #612 by @char0n
  - Clarification around URL resolution rules (#782) ([fc324ef](https://github.com/asyncapi/spec/commit/fc324ef3aa92d313918a00ea9a5eb6c85720a36d)), closes #674 by @char0n
  - Align wording with [RFC 2119](https://www.rfc-editor.org/rfc/rfc2119) (#818) ([5580a9c](https://github.com/asyncapi/spec/commit/5580a9c5fbef55e925e7514b986c95a0e4c85821)) by @char0n

Fixes
---
- Added missing IBM MQ Operation Binding (#840) ([68d85d1](https://github.com/asyncapi/spec/commit/68d85d19e5be12fa6e13d0fc5851993934dbdcde)) ([binding definition](https://github.com/asyncapi/bindings/tree/master/ibmmq#operation-binding-object)), refs [#605](https://github.com/asyncapi/spec/issues/605) by @magicmatatjahu

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

@fmvilas
Copy link
Member

fmvilas commented Sep 28, 2022

Wanna do the honors @derberg? I'm afraid I'll break something 😂

@derberg
Copy link
Member

derberg commented Sep 28, 2022

@char0n but this is a PR from your fork, and should be from next-spec

@char0n
Copy link
Collaborator Author

char0n commented Sep 28, 2022

Closing in favor of #842

@char0n char0n closed this Sep 28, 2022
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.

7 participants