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

Bump version on master #3658

Merged
merged 1 commit into from Apr 27, 2024
Merged

Bump version on master #3658

merged 1 commit into from Apr 27, 2024

Conversation

kchibisov
Copy link
Member

This commit does not represent a release and only synchronizes CHANGELOG from the latest release.

This commit does not represent a release and only synchronizes CHANGELOG
from the latest release.
Copy link
Member

@madsmtm madsmtm left a comment

Choose a reason for hiding this comment

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

Approved, though the git history seems weird to me, I'd assume that when doing a breaking release we would base the 0.30.x branch off of master?

@kchibisov
Copy link
Member Author

Approved, though the git history seems weird to me, I'd assume that when doing a breaking release we would base the 0.30.x branch off of master?

new 0.31.x branch will be created. Everything is according to our CONTRIBUTING guidelines.

@kchibisov kchibisov merged commit 337d507 into master Apr 27, 2024
52 checks passed
@kchibisov kchibisov deleted the kchibisov/sync-0300 branch April 27, 2024 16:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants