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, ...)
Merging the changes of v3.0.0 release to develop.

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-AidenJ
Copy link
Contributor

Looks good!

@CDR-AidenJ CDR-AidenJ closed this Apr 1, 2025
@CDR-AidenJ CDR-AidenJ reopened this Apr 1, 2025
@CDR-AidenJ CDR-AidenJ self-requested a review April 1, 2025 02:25
@sonarqubecloud
Copy link

sonarqubecloud bot commented Apr 1, 2025

@CDR-AidenJ CDR-AidenJ enabled auto-merge (squash) April 1, 2025 02:52
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!

@CDR-AidenJ CDR-AidenJ merged commit 28a92ff into develop Apr 1, 2025
13 checks passed
@CDR-AidenJ CDR-AidenJ deleted the releases/3.0.0 branch April 3, 2025 04:05
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