Skip to content

v2.4.0 (2022-05-19) Branch deployments & support for AsyncAPI 2.4
Compare
Choose a tag to compare
@github-actions github-actions released this 19 May 12:28
· 122 commits to main since this release
v2.4.0
4232d7c
This commit was signed with the committer’s verified signature. The key has expired.
paulRbr Paul B.
GPG key ID: DE331B23748D3A27
Expired
Learn about vigilant mode.

🆕 diff and deploy commands accepts a new --branch argument

  • Both the diff & deploy commands will now accept a --branch argument so you can deploy new versions of your API reference in a separate branch. By default, when you don't use the argument all new versions are deployed to a default main branch.

    This new feature is useful when you want to keep multiple history available on your API documentation. For example, you might want to deploy all your newest API changes on a latest branch (with the new --branch latest argument), and when happy about the latest changes, you decide to release to the main default branch (by removing the --branch ... argument).

🆙 Support for the latest 2.4 release of AsyncAPI specification

  • AsyncAPI recently release their 2.4 version. Check out their blog post announcement: https://www.asyncapi.com/blog/release-notes-2.4.0
    With this new release of the Bump CLI we partially support the latest changes of the AsyncAPI spec.

  • Thanks to @dependabot, all the node dependencies we use are up-to-date as of today.

Have fun designing APIs and our new branching mechanism 🌳 ✨

Contributors

dependabot
Assets 8
Loading