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.6.0.Beta18 [4th attempt] #1444

Merged
merged 1 commit into from
Dec 12, 2024

Conversation

michalvavrik
Copy link
Member

Summary

Latest attempt in a popular series I performed today (#1439, #1436, #1430, #1432). Now I hope for a different results because I changed the release workflow #1441 and then fixed that fix twice (#1442, #1443).

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
  • Release (follows conventions described in the RELEASE.md)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • This change requires a documentation update
  • This change requires execution against OCP (use run tests phrase in comment)

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 merged commit 6dc7218 into main Dec 12, 2024
2 of 8 checks passed
@michalvavrik michalvavrik deleted the release/1.6.0.Beta18-4th-attempt branch December 12, 2024 18:48
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.

1 participant