Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 1.2.0.Beta2 #517

Merged
merged 1 commit into from
Jul 19, 2022
Merged

Release 1.2.0.Beta2 #517

merged 1 commit into from
Jul 19, 2022

Conversation

michalvavrik
Copy link
Member

@michalvavrik michalvavrik commented Jul 19, 2022

Summary

Release 1.2.0.Beta2 and set next version to 1.2.0.Beta3.

Please check the relevant options

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Dependency update
  • Refactoring
  • Breaking change (fix or feature that would cause existing functionality to change)
  • This change requires a documentation update
  • Release

Checklist:

  • Example scenarios has been updated / added
  • Methods and classes used in PR scenarios are meaningful
  • Commits are well encapsulated and follow the best practices

@michalvavrik michalvavrik requested a review from pjgg July 19, 2022 12:04
Copy link
Contributor

@pjgg pjgg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Wait to CI please

@pjgg pjgg merged commit 083c5bc into main Jul 19, 2022
@michalvavrik michalvavrik deleted the feature/release121-beta1 branch July 19, 2022 13:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants