Skip to content

Conversation

@mikeweis
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!

@mikeweis mikeweis self-assigned this Dec 16, 2025
@codecov
Copy link

codecov bot commented Dec 16, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@mikeweis mikeweis merged commit bc580bf into main Jan 5, 2026
16 checks passed
@mikeweis mikeweis deleted the SITES-38543-disable-canonical-from-paid branch January 5, 2026 16:56
solaris007 pushed a commit that referenced this pull request Jan 5, 2026
# [1.279.0](v1.278.5...v1.279.0) (2026-01-05)

### Features

* disable the canonical audit from paid customers ([#1663](#1663)) ([bc580bf](bc580bf))
@solaris007
Copy link
Member

🎉 This PR is included in version 1.279.0 🎉

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.

4 participants