fix: revalidateTag not reaching custom cache handlers when profiles differ (#99359)
Fix `updateTags` skipping cache handlers when a request uses multiple
cache profiles.
## Why
`getCacheHandlers()` returns a one-time iterator. When tags are grouped
by profile, the first group consumes the iterator, so subsequent groups
don't reach any handlers.
This is especially noticeable with custom cache handlers, where tags may
not be propagated to other instances.
## How
Convert the handlers iterator to an array once and reuse it for each
profile group.
## Test
Added an E2E test covering `updateTag()` and `revalidateTag()` with
different profiles.
Fixes #99352
---------
Co-authored-by:
Claude Opus 5.5 <noreply@anthropic.com>
Showing
Please
register
or
sign in
to comment