fix: invalidate cache on any Tenant update #1591
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
edgurgel
force-pushed
the
fix/invalidate-cache-on-any-tenant-change
branch
from
e0795d0 to
aed1b0b
Compare
filipecabaco
approved these changes
Oct 29, 2025
edgurgel
force-pushed
the
fix/invalidate-cache-on-any-tenant-change
branch
from
aed1b0b to
0b7ad8a
Compare
|
🎉 This PR is included in version 2.57.6 🎉 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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
Invalidate cache on any Tenant update
What is the current behavior?
It was invalidating only for a specific set of changes
What is the new behavior?
Any change triggers cache invalidation
Additional context
Add any other context or screenshots.