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.

Sign up for GitHub

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

Jump to bottom

Release/1.3.1 #1195

Merged
merged 1 commit into from
Jul 9, 2024
Merged

Release/1.3.1 #1195

merged 1 commit into from
Jul 9, 2024

Conversation

fedinskiy
Copy link
Contributor

Summary

Release 1.3.1

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
  • 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

@fedinskiy fedinskiy requested a review from michalvavrik July 9, 2024 11:37
@fedinskiy fedinskiy changed the base branch from main to 1.3.z July 9, 2024 11:37
@michalvavrik michalvavrik merged commit 424218e into 1.3.z Jul 9, 2024
@michalvavrik michalvavrik deleted the release/1.3.1 branch July 9, 2024 11:51
@michalvavrik
Copy link
Member

hmm, zero checks confused me :-D I thought that checks are green because they are already finished. not sure why they didn't start for 13 minutes, anyway, we just merged PR that tested current 1.3.z head, so I am not worried.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@michalvavrik michalvavrik michalvavrik approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@fedinskiy @michalvavrik