Skip to content

Conversation

@CDR-FarooqK
Copy link
Contributor

Checklist: (Put an x in all the boxes that apply)

  • I have read the CONTRIBUTING document.
  • My code follows the code style of this project.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.
  • I have checked that there aren't any other open Pull Requests from the same change.
  • The develop branch has been set as the base branch to merge changes of the pull request.
  • I have updated the CHANGELOG.md file as appropriate.

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
v2.1.0 release

What is the current behavior? (You can also link to an open issue here)

What is the new behavior? (if this is a feature change)

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

Other information:

@CDR-FarooqK CDR-FarooqK requested a review from CDR-AidenJ August 16, 2024 00:26
@sonarqubecloud
Copy link

sonarqubecloud bot commented Aug 16, 2024

Copy link
Contributor

@CDR-AidenJ CDR-AidenJ left a comment

Choose a reason for hiding this comment

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

Looks good to me!

@CDR-FarooqK CDR-FarooqK merged commit e3e222e into develop Aug 19, 2024
@CDR-FarooqK CDR-FarooqK deleted the releases/2.1.0 branch August 22, 2024 23:09
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.

4 participants