chore: update next-spec branch with master changes #249
Conversation
char0n
requested review from
fmvilas,
derberg,
dalelane and
asyncapi-bot-eve
as code owners
|
Kudos, SonarCloud Quality Gate passed!
|
|
@fmvilas @derberg @dalelane would you mind reviewing this PR please? Thanks Verification question - I've created this PR by merging master branch with next-spec and issuing a PR containing the merges + a merge commit. There are other ways to achieve the same. Is there any preference in how to achieve the goal of updating the next-spec branch from master? If yes please let me know. |
There was a problem hiding this comment.
@char0n we did not standardize the flow here. I would also just merge master into next.
I think we should consider having a workflow that will always keep next branches up to date with master, on a regular basis between releases. This can be automated with https://github.com/marketplace/actions/update-git-branch and means one manual step less.. Just put it as followup release process improvement actions after release.
|
/rtm |
ACKN.
Added in asyncapi/spec#830 |
|
🎉 This PR is included in version 3.2.0-next-major-spec.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 2.15.0-next-spec.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 3.2.0-next-spec.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 3.2.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This is PR is part of asyncapi/spec#830 and updates
next-specbranch with changes frommaster.