api@2.1.1

Bug Fixes

• Update to v5 (#8)

api@2.1.0

New Features

• Feature D (#6)

  This should initially fail to publish due to the ambiguity of v2.0.1 being published from release branch a. It should successfully publish as v2.1.0 when --versioning ALWAYS_INCREASING is passed.

api@1.1.2

Bug Fixes

• A fix to release b (#7)

  Once the manifest is updated to allow versioning by branch, this can be released as 1.1.2

api@2.0.1

Bug Fixes

• A bug fix for testing (#5)

api@2.0.0

Breaking Changes

• This one is a breaking change (#3)

api@1.1.1

Bug Fixes

• A bug fix on an older major version using --version-by-branch (#4)

api@1.1.0

New Features

• Use new backend (#2)

api@1.0.0

New Features

• Initial release (#1)