Skip to content

Conversation

radhikagpt1208
Copy link
Contributor

Please ensure your pull request adheres to the following guidelines:

  • make sure to link the related issues in this description. Or if there's no issue created, make sure you
    describe here the problem you're solving.
  • when merging / squashing, make sure the fixed issue references are visible in the commits, for easy compilation of release notes

If the PR is changing the API specification:

  • make sure you add a "Not implemented yet" note the endpoint description, if the implementation is not ready
    yet. Ideally, return a 501 status code with a message explaining the feature is not implemented yet.
  • make sure you add at least one example of the request and response.

If the PR is changing the API implementation or an entity exposed through the API:

  • make sure you update the API specification and the examples to reflect the changes.

If the PR is introducing a new audit type:

  • make sure you update the API specification with the type, schema of the audit result and an example

Related Issues

Thanks for contributing!

Copy link

This PR will trigger a patch release when merged.

@radhikagpt1208 radhikagpt1208 merged commit c957382 into main Sep 10, 2025
7 checks passed
@radhikagpt1208 radhikagpt1208 deleted the update-lorem-ipsum-check-name branch September 10, 2025 06:07
solaris007 pushed a commit that referenced this pull request Sep 10, 2025
## [1.177.3](v1.177.2...v1.177.3) (2025-09-10)

### Bug Fixes

* updating lorem-ipsum check name in preflight ([#1237](#1237)) ([c957382](c957382))
@solaris007
Copy link
Member

🎉 This PR is included in version 1.177.3 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants