chore(release): bump version to 1.13.0#109
Merged
Merged
Conversation
Release the changes merged since v1.12.0: - fix(account): rename ReservedBalance.amounts to availableAmounts (#108) - feat(cc): adding cc bill dates (#107) Minor rather than patch because of the feat in #107. Merging this to master triggers release.yml, which tags v1.13.0 and cuts the GitHub Release. Publishing the jar to GitHub Packages is a separate manual step (see #106): gh workflow run maven-publish.yml -f tag_version=v1.13.0
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Release the changes merged since
v1.12.0:fix(account): renameReservedBalance.amountstoavailableAmounts(fix(account): rename ReservedBalance.amounts to availableAmounts #108)feat(cc): adding cc bill dates (feat(cc): adding cc bill dates #107)Minor rather than patch because of the feat in #107.
v1.12.0was already tagged, so the last two merges did not cut a release —release.ymlloggedTag v1.12.0 already exists, skipping release. This bump is what lets it tag again.After merge
Merging triggers
release.yml, which tagsv1.13.0and cuts the GitHub Release. Publishing the jar to GitHub Packages is a separate manual step (#106), since the Release is created with the defaultGITHUB_TOKENand GitHub does not fire workflow triggers for those events:Until that dispatch runs,
availableAmountsis not available to consumers of this SDK.Test plan
pom.xmlhad exactly one<version>1.12.0</version>occurrence.gh release view v1.13.0, then the manualmaven-publish.ymldispatch and its deploy job