Repository navigation
chore: compare against 0.2.0 and document the release steps - #66
Merged
Merged
Conversation
- CompatibilityIT baseline 0.2.0 with no expected changes (the 22 requests answer exactly like the published release). - CONTRIBUTING: release order as done for 0.2.0 - merge, tag, deploy from the tag, then the GitHub release on the existing tag.
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
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.
After releasing 0.2.0:
CompatibilityITnow compares against 0.2.0 with no expected changes: all 22 requests answer exactly like the published release.CONTRIBUTING.md: the release steps in the order used for 0.2.0 — merge tomain, tag,mvn clean deployfrom the tag, then the GitHub release on the existing tag (the workflow attaches the jars).Verified locally:
mvn clean verifygreen (143 unit + 11 IT).